I'm surprised that it doesn't support Python 3.5. I've been a bit out of touch with Python - is there something that changed significantly in subsequent versions to justify this?
He said he under appreciated how big the community would get but also the number of people who would use it.
He faulted himself for not spending time thinking about the transition from him primarily working on it to others. And that he should have been thinking about how things would work when he was not involved.
The specific item he was concerned about was that he did not work to build a "community of like minded people" which he says Django did a much better job at doing.
At the very end of the comment, he openly considers if there are things he should have done differently:
"I probably would feel less detached from it if I would have communicated some of my ideas more.
I feel like it is no longer my fight to make it more backwards compatible for instance. The community sees this differently than I do, so that's fine."
I don't know too much about it but raymond hettinger gave a talk about it. https://www.youtube.com/watch?v=p33CVV29OG8
- Add type hinting. https://github.com/pallets/flask/pull/3973
I think it's fair to assume annotations is the big reason.
[0] https://docs.python.org/3/whatsnew/3.6.html#whatsnew36-compa... [1] https://mail.python.org/pipermail/python-dev/2017-December/1...
They are now insertion ordered.
I’m guessing they want to tell people it’s time to upgrade. And 3.6 brings a lot of niceties that they might want to use, like f-strings.
If you haven't updated in that time, you probably have a systemic problem which shouldn't be blamed on Python moving too fast (in fact I suspect those people don't keep up with bugfixes either, so nudging them to upgrade when they try to update flask/numpy is a good idea).
I imagine that removing it from the supported versions in Flask allows for example to use f-strings.
(Current is 3.9 so 8,7,6 are also supported)