Closed Houkime closed 2 years ago
Ok, so my exact problem with this (mentioned right above) was occuring on Arch Linux.
requirements.txt
does actually forbid apispec from crossing 4.0.0 but the Arch package
https://www.archlinux.org/packages/community/any/python-aiohttp-apispec/
does not account for that and allows to use apispec 4.0.0.
So, currently aiohttp_apispec is broken on Arch if installed from pacman and works if installed from pip. Notified maintainer.
cc @felixonmars
Opened Arch bug report at https://bugs.archlinux.org/task/68874
Closed with #115
The change was introduced in https://github.com/marshmallow-code/apispec/commit/ee8002b466aeebb753bdf93047198b3ff63f02d0
And
apispec
4.0.0 went live on september 30 with this included.The new signature is like here (openapi.py, comments included so that constraints are clearer):
(take note that "body" is not allowed in OpenAPI 3)