Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Remove coreapi requirement
See original GitHub issueDescription
The coreapi requirement should be removed from requirements/base.txt.
Rationale
From the CoreAPI page:
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.
The DRF 3.9 page has an example of how to use the integrated OpenAPI support.
Use case(s) / visualization(s)
None. It’s a requirement for a module no longer developed. If it’s used somewhere in the template that I’ve missed, it should be replaced with OpenAPI equivalents.
I only noticed it because I’m going through a Django project generated by this cookiecutter and can’t explain why the requirement exists.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
coreapi has clearly been deprecated by DRF (see the 3.10 release announcement) The method of generating documentation given above is no longer recommended in the docs.
so what’s the fix just remove the line from requirements.txt?