3 ms·

A bit off topic, but does anybody know why development looks stopped since 2013? http://flask.pocoo.org/docs/0.10/changelog/ http://flask.pocoo.org/docs/0.10/ch

by kunoo 11y ago

A bit off topic, but does anybody know why development looks stopped since 2013? http://flask.pocoo.org/docs/0.10/changelog/ http://flask.pocoo.org/docs/0.10/changelog/ I'm in the process of writing my first webapp, and thses days it's a bit strange seeing a popular framework not being updated (even if it's just for bugfixing) a few times a year.

detaro 11y ago
It hasn't stopped, there just hasn't been a release. Main issue seems to be that the next release was planned to be the magic "1.0" and that isn't finished. So while that is worked on, there haven't been new releases, because the current release works, and most bug fixes happened in dependencies (jinja, werkzeug). At least that was my takeaway from various github discussions about it.
zanny 11y ago
There are milestones for 0.11 and 1.0: https://github.com/mitsuhiko/flask/milestones/0.11 https://github.com/mitsuhiko/flask/milestones/0.11 https://github.com/mitsuhiko/flask/milestones/1.0 https://github.com/mitsuhiko/flask/milestones/1.0 None of the 0.11 blockers are substantial, and 1.0 is mostly about having updated documentation. It just requires someone to actually finish them.
andrewstuart 11y ago
It's a bit unclear how enthused Mitsuhiko remains about Python development. He is one of the greatest contributors to the Python community and undoubtedly one of the most impressive software developers on the Internet. He is very "Python 2" oriented though and I wonder if his enthusiasm for Python has waned because he could never get onboard the Python 3 thing with enthusiasm. To his credit he updated Flask early to Python 3 and he has written alot of other stuff, most of which I understand to be Python 3 compatible. As everyone here knows, it's hard to write software when you don't feel enthused about the programming language. He has been doing stuff with Rust in particular. Maybe there will be a "Rusty Flask" one day.
- leejoramo 11y ago
  I have done a little Flask work, but can't say that I have really followed Mitsuhiko's work. However, I have been looking at extensively digging into his new python based Lektor CMS https://github.com/lektor https://github.com/lektor
  - andrewstuart 11y ago
    Apparently his enthusiasm remains high!
matthewowen 11y ago
It's important to understand that Flask is really, really, really tiny. Most of the meaningful code about handling requests etc etc etc is in Werkzeug. Flask is really a small layer adding some convenience functions and tying into templating.
- untitaker_ 11y ago
  Werkzeug is also under Mitsuhiko's control and has similar maintenance problems.
- pyre 11y ago
  This is very true. I can't count the number of times that I've had to dive into werkzeug code while trying to figure out how Flask was doing something.
the_mitsuhiko 11y ago
> A bit off topic, but does anybody know why development looks stopped since 2013? It did not stop, it just did not get a release. I'm (very slowly unfortunately) in the process of fixing this by restructuring the github org to get trusted contributors to fix this and to make it easier to have multiple smaller releases instead of a huge one. There is always risk in pushing out releases with a lot of changes which is what would happen which is why I want to have people in place that can push releases without my help to fix things if they are regressing. I would have done it over Christmas already but life keeps happening and this is something I rather not do without having an action plan :) Very soon now though.
davidism 11y ago
For more information, the current discussion about a new release is at https://github.com/mitsuhiko/flask/issues/1575#issuecomment-145716465 https://github.com/mitsuhiko/flask/issues/1575#issuecomment-...

by kunoo 11y ago

detaro 11y ago

It hasn't stopped, there just hasn't been a release. Main issue seems to be that the next release was planned to be the magic "1.0" and that isn't finished. So while that is worked on, there haven't been new releases, because the current release works, and most bug fixes happened in dependencies (jinja, werkzeug). At least that was my takeaway from various github discussions about it.

zanny 11y ago

There are milestones for 0.11 and 1.0: https://github.com/mitsuhiko/flask/milestones/0.11 https://github.com/mitsuhiko/flask/milestones/0.11 https://github.com/mitsuhiko/flask/milestones/1.0 https://github.com/mitsuhiko/flask/milestones/1.0 None of the 0.11 blockers are substantial, and 1.0 is mostly about having updated documentation. It just requires someone to actually finish them.

andrewstuart 11y ago

It's a bit unclear how enthused Mitsuhiko remains about Python development. He is one of the greatest contributors to the Python community and undoubtedly one of the most impressive software developers on the Internet. He is very "Python 2" oriented though and I wonder if his enthusiasm for Python has waned because he could never get onboard the Python 3 thing with enthusiasm. To his credit he updated Flask early to Python 3 and he has written alot of other stuff, most of which I understand to be Python 3 compatible. As everyone here knows, it's hard to write software when you don't feel enthused about the programming language. He has been doing stuff with Rust in particular. Maybe there will be a "Rusty Flask" one day.

leejoramo 11y ago
I have done a little Flask work, but can't say that I have really followed Mitsuhiko's work. However, I have been looking at extensively digging into his new python based Lektor CMS https://github.com/lektor https://github.com/lektor
- andrewstuart 11y ago
  Apparently his enthusiasm remains high!

matthewowen 11y ago

It's important to understand that Flask is really, really, really tiny. Most of the meaningful code about handling requests etc etc etc is in Werkzeug. Flask is really a small layer adding some convenience functions and tying into templating.

untitaker_ 11y ago
Werkzeug is also under Mitsuhiko's control and has similar maintenance problems.
pyre 11y ago
This is very true. I can't count the number of times that I've had to dive into werkzeug code while trying to figure out how Flask was doing something.

the_mitsuhiko 11y ago

> A bit off topic, but does anybody know why development looks stopped since 2013? It did not stop, it just did not get a release. I'm (very slowly unfortunately) in the process of fixing this by restructuring the github org to get trusted contributors to fix this and to make it easier to have multiple smaller releases instead of a huge one. There is always risk in pushing out releases with a lot of changes which is what would happen which is why I want to have people in place that can push releases without my help to fix things if they are regressing. I would have done it over Christmas already but life keeps happening and this is something I rather not do without having an action plan :) Very soon now though.

davidism 11y ago

For more information, the current discussion about a new release is at https://github.com/mitsuhiko/flask/issues/1575#issuecomment-145716465 https://github.com/mitsuhiko/flask/issues/1575#issuecomment-...