-
Notifications
You must be signed in to change notification settings - Fork 151
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
Breaking Changes in webargs 6.0.0b1 (pre-release) #176
Comments
Got the same error and spent far too long debugging it. |
Looks like webargs released 6.0.0 yesterday! This is no longer just an issue with a pre-release package. Anyone installing flask-apispec without an explicit |
flask-apispec 0.8.6 restricts the webargs version to <6.0. I'll open a new issue to fix compatibility with >=6.0 |
jollysahil
pushed a commit
to levrofin/flask-apispec
that referenced
this issue
Sep 12, 2023
webargs 6.0.0 has incompatible changes for example: - Parser.use_args and Parser.use_kwargs now accept location (singular) instead of locations (plurala) close: jmcarp#176
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, just ran into this by accident and wanted to be sure this landed on your radar. Webargs has introduced a backwards-incompatible v6 pre-release. https://webargs.readthedocs.io/en/latest/changelog.html#b1-2020-01-06
You may want to pin webargs to
<6.0.0
until you come up with a more thoughtful approach.To Recreate
Example flask app:
Dependencies: (
requirements.txt
)Error:
The text was updated successfully, but these errors were encountered: