You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DEPRECATION NOTICE: As of djangorestframework 3.9, the plan is to phase out CoreAPI in favor of OpenAPI as the default schema representation. New projects should consider using OpenAPI rather than CoreAPI. See the DRF 3.9 release announcment for more details.
Another benefit of removing the dependency on coreapi is that coreapi depends on requests, which depends on chardet. chardet is LGPL licensed which presents problems for developers wanting to package their application as a binary using PyInstaller or PyOxidizer (psf/requests#4417).
Seems like we should try to identify and migrate over the parts of coreapi that are needed for drf-yasg2.
Upsteam issues:
From the
core-api
repo:DRF will soon be raising deprecation warnings for CoreAPI schemas and they will be removed in DRF 3.14. I haven't looked closely enough at
drf-yasg2
to know if this will affect this package, or if we only rely oncoreapi
directly rather than through DRF itself.The
coreapi
Python package is frozen and has not seen a release in 3 years. It was last tested on Python 3.6. This is a liability for the long term health of this project. This upstream issue would have brokendrf-yasg[2]
on Python 3.10, but a maintainer took over one ofcoreapi
's frozen dependencies,itypes
and fixed the issue.Another benefit of removing the dependency on
coreapi
is thatcoreapi
depends onrequests
, which depends onchardet
.chardet
is LGPL licensed which presents problems for developers wanting to package their application as a binary using PyInstaller or PyOxidizer (psf/requests#4417).Seems like we should try to identify and migrate over the parts of
coreapi
that are needed fordrf-yasg2
.coreapi
also brings incoreschema
which is used bydrf-yasg2
.coreschema
has also not been maintained for 3 years.The text was updated successfully, but these errors were encountered: