-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
Version 3.10.1 #6817
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
Version 3.10.1 #6817
Conversation
rest_framework/compat.py
Outdated
except ImportError: | ||
coreapi = None | ||
|
||
# uritemplate is required for OpenAPI schema generation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
uritemplate is required for both CoreAPI and OpenAPI schema generation.
I'm having some issues building the release on my machine. @carltongibson any chance you'd be able to try giving it a go? Failing that I'll be able to try from my work machine tomorrow. I keep getting "Checking distribution dist/djangorestframework-3.10.1-py3-none-any.whl: warning: I tried just pushing it to PyPI regardless but that failed with the same error and a 400. |
Managed to deploy to PyPI, but I needed to entirely drop the long_description in order to get there. 😕 |
I'm guessing you have an outdated version of wheel installed - probably running into #4012 (comment) |
Maybe. I created a completely clean virtualenv, so it’s not obvious to me how that’d be, but I’ll take a deeper look next time. |
What version of wheel is installed? Can you run a quick |
* Ensure that requiring 'uritemplate' does not also require 'coreapi' * Don't include autocomplete fields on TokenAuth admin * Version 3.10.1
* Ensure that requiring 'uritemplate' does not also require 'coreapi' * Don't include autocomplete fields on TokenAuth admin * Version 3.10.1
Ensure that requiring uritemplate, doe not also require coreapi
Refs #6814
Don't include autocomplete fields on TokenAuth admin
Closes #6808
Refs #6762
I think we should instead document how to customize the TokenAuth admin, using an
autocomplete
field as an example case. (Looking into it I can see that expanding on #3831 slightly is what we'd want)Also closes #6811