As a user of Flask and Dash, the locking is very annoying. I understand that you can have issues with a new version of Flask. A log My suggestion is to work and fix the problem. If you want to have a silo, Dash creates a new package. Not sure what it is your user distribution, but most of the people I know are using Flask and Dash. Definitively this part of users are frustrated.
PyPI Download Stats Downloads last month: 79,956,762
PyPI Download Stats Downloads last month: 1,708,872
Any update on this topic? As a user who integrated Dash in a Flask app, I would really appreciate any communication regarding your further plans. Thank you in advance
I appreciate everyone’s patience with this process. We’re almost ready to bump the limit in Dash, we just have a couple of other packages on our enterprise side that need to have patches published with their own limits on Flask and Werkzeug. Once that’s done we’ll test and publish a new Dash release with the Flask and Werkzeug limits raised to <3.1. I expect we’ll be able to do this by next week.
Again, because of the history of breakage we are NOT intending to remove this limit entirely, but once our other packages ensure their own safety independently, it should be easier for us to quickly raise the limit on Dash itself each time a new Flask minor is released.
Dash v2.14.1 was just released, and raises the upper limit on Flask (and Werkzeug) to <3.1, to support the latest release. If you’re using any Dash Enterprise packages that use Flask directly, these are still limited to <2.3 for the moment but we’ll be increasing that limit soon.
Going forward, now that we can do this without simultaneously testing all of our other packages, we’ll try to bump these limits right away whenever there’s a new Flask minor or major release, but if we don’t notice it immediately and you need the new version, feel free to create the PR yourself, like the PR included in 2.14.1: