-
Notifications
You must be signed in to change notification settings - Fork 190
Release version will not run on current release of Flask! #168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
what about #166? |
I can confirm that this issue still persists, and flask cannot be started:
@jacebrowning @auvipy are you able to make a new release for flask-api? |
Current workaround until new release:
|
Hi! I'm currently having the same issue. I've seen v3.2 might have been completed on February. Is there any plan to upload it to Pypi? Thanks in advance! |
…Is this repo dead? The last commit was made over a year ago, and even though said commit (which happens to be the only commit made in the last year) changes the package version number to v3.2, there was neither a release on PyPI nor even a git tag for it 🤔 |
I get a similar error:
After doing,
it works. Could someone release a new version of |
Flask 3.0.2 relies on Werkzeug 3 which removed werkzeug.urls that Flask-api Release relies on, resulting in
cannot import name 'url_decode_stream' from 'werkzeug.urls
Looks like the issue was fixed in Oct in Develop branch (161?) and I can confirm the error is gone with a manual Pip install from the develop branch zip.
But, since your setup just requires ["Flask >= 2.0.0"] a simple hello world using pip install flask flask-api will get Flask 3.02 and Flask-api will break.
Please consider an urgent merge & release since for the average new user ( not developer) Flask-api just won't work!
The text was updated successfully, but these errors were encountered: