-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Flask-Common not compatible with Flask-1.0 #442
Comments
BTW, the issue has occurred after |
I suggest pinning to |
javabrett
added a commit
to javabrett/httpbin
that referenced
this issue
May 2, 2018
…hilst compat with Flask 1.0.1 is worked-on.
javabrett
added a commit
to javabrett/httpbin
that referenced
this issue
May 5, 2018
javabrett
added a commit
to javabrett/httpbin
that referenced
this issue
May 6, 2018
This was referenced May 6, 2018
sigmavirus24
added a commit
that referenced
this issue
May 6, 2018
Removed Flask-Common. Fixed #442.
javabrett
added a commit
to javabrett/httpbin
that referenced
this issue
May 7, 2018
…hilst compat with Flask 1.0.1 is worked-on.
virgiliojr94
pushed a commit
to virgiliojr94/httpbin-chat2desk
that referenced
this issue
Jul 1, 2023
virgiliojr94
pushed a commit
to virgiliojr94/httpbin-chat2desk
that referenced
this issue
Jul 1, 2023
…mmon Removed Flask-Common. Fixed postmanlabs#442.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Requests test suit broke a couple hours ago with the release of Flask-1.0. The flask-common module in httpbin relies on the
flask.exthook
module which was removed, so we now get import errors. We can either updateflask-common
which seems to have been moved into read-only mode on Github, we pinFlask<1.0
, or we can remove it as a dependency.@kennethreitz do you have any opinion on this? If it's not going to be maintained, I propose we do a one time update to be tolerant of Flask-1.0 changes, and then move to deprecate.
The text was updated successfully, but these errors were encountered: