4 ms·

They should really name it Flask 1.0 at this point, as it's a very mature library and lots of people (including me) use it in production settings. In my humble

They should really name it Flask 1.0 at this point, as it's a very mature library and lots of people (including me) use it in production settings. In my humble opinion, the 0.11 version number tends to shy people away from the library as it conveys the impression that it's still heavily evolving or not well-tested, which is not the case. In any case: Congrats :)

frewsxcv 10y ago
The version number is 0.11, which is different from 0.1.
- ThePhysicist 10y ago
  good point, changed it :)
gedrap 10y ago
But does it really matter now that Flask is so popular? Probably not :)
w4 10y ago
When I decided to learn web dev (coming from a native background), the lack of updates to Flask was more of a concern than the 0.11 version number. Everything I read online said that Flask was rock solid, so getting stuck with an abandoned framework in production was my main concern. Glad to see Flask's development is back on track, and under formal management!
- Marazan 10y ago
  Flask development has never not been on track, there have been plenty of commits and bug fixes in the last 3 years, theyve just never made a official release until now.
  - w4 10y ago
    I'm aware, but a web framework going 3 years without a release renders the distinction between "no releases" and "no development" more or less meaningless from an end user's point of view.
    - zeckalpha 10y ago
      Or it means the APIs are stable, and the feature set is sufficiently limited to avoid bloat.
      - prokaktus 10y ago
        And new releases could be 0.10.2, 0.10.3, ..., with fixes included! And I'm ok with that from user point of view. But Flask package stuck with 0.10.1. Glad to see 0.11!
zanny 10y ago
They have a 1.0 milestone, so fix all the issues tracking for it and we would get it! I believe the main blocker is updated documentation. https://github.com/pallets/flask/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0 https://github.com/pallets/flask/issues?q=is%3Aopen+is%3Aiss...

frewsxcv 10y ago

The version number is 0.11, which is different from 0.1.

ThePhysicist 10y ago
good point, changed it :)

gedrap 10y ago

But does it really matter now that Flask is so popular? Probably not :)

w4 10y ago

When I decided to learn web dev (coming from a native background), the lack of updates to Flask was more of a concern than the 0.11 version number. Everything I read online said that Flask was rock solid, so getting stuck with an abandoned framework in production was my main concern. Glad to see Flask's development is back on track, and under formal management!

Marazan 10y ago
Flask development has never not been on track, there have been plenty of commits and bug fixes in the last 3 years, theyve just never made a official release until now.
- w4 10y ago
  I'm aware, but a web framework going 3 years without a release renders the distinction between "no releases" and "no development" more or less meaningless from an end user's point of view.
  - zeckalpha 10y ago
    Or it means the APIs are stable, and the feature set is sufficiently limited to avoid bloat.
    - prokaktus 10y ago
      And new releases could be 0.10.2, 0.10.3, ..., with fixes included! And I'm ok with that from user point of view. But Flask package stuck with 0.10.1. Glad to see 0.11!

zanny 10y ago

They have a 1.0 milestone, so fix all the issues tracking for it and we would get it! I believe the main blocker is updated documentation. https://github.com/pallets/flask/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0 https://github.com/pallets/flask/issues?q=is%3Aopen+is%3Aiss...