Skip to content
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

URLPathVersioning should maybe remove the version_param kwarg from subsequent view dispatch? #3718

shabble opened this issue Dec 9, 2015 · 3 comments · Fixed by #3723


Copy link

shabble commented Dec 9, 2015

I've been playing around with getting URLPathVersioning working properly, and have discovered what might be a bug, or maybe just undocumented (or obvious and expected) behaviour.

urlconf contains:

from rest_framework.authtoken.views import obtain_auth_token
# ...

api_patterns = [
    url(r'^', include(router.urls), name='api-root'),
    url(r'^auth-token/', obtain_auth_token, name='api-auth-token'),
urlpatterns = [
    url(r'^api/(?P<version>v\d{1,})/', include(api_patterns)),
    # ...

When testing, with something like:

url = reverse('api-auth-token', kwargs=dict(version='v1')), data, format='json')

I get an exception that ultimately ends in:

  File "/usr/local/lib/python2.7/dist-packages/rest_framework/", line 463, in dispatch
    response = handler(request, *args, **kwargs)
TypeError: post() got an unexpected keyword argument 'version'

Investigation shows that the method doesn't accept any kwargs, so it's clearly failing because it's getting version passed in by default from the rest of the versionating mechanism.

Simplest fix would be to just fix the definition of, request, **kwargs),
but it made me wonder if it'll be an issue for other views that are receiving a somewhat unexpected kwarg, and which is by intent already available to them in request.version.

If there's no good reason to keep it around after extracting it, would it make sense to clean it from the
view args in views.APIView somewhere in the initial pre-dispatch phases, maybe as simple as a
kwargs.pop(request.versioning_scheme.version_param, None) (with some checks around it) in the appropriate place?

I'm currently subclassing authtoken.ObtainAuthToken to do exactly this in post(), but I figured it might make sense to raise a a more general issue.

Copy link

xordoquy commented Dec 10, 2015

I'd rather fix the AuthToken to accept the extra kwarg.

@xordoquy xordoquy added this to the 3.3.2 Release milestone Dec 10, 2015
Copy link

xordoquy commented Dec 10, 2015

Thanks for reporting.

Copy link

tomchristie commented Dec 10, 2015

I'd rather fix the AuthToken to accept the extra kwarg.

Seems reasonable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

Successfully merging a pull request may close this issue.

3 participants