Support URLPattern and URLResolver from Django 2.0 #5500
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
carltongibson
approved these changes
Oct 16, 2017
There was a problem hiding this comment.
@mkuznets Great stuff. Really clears up the test suite a lot!
Thanks for the input.
This was referenced Oct 16, 2017
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #5456
My attempt to make sense of the new URL routing API from Django 2.0:
RegexURLPatternandRegexURLResolverare renamed toURLPatternandURLResolverrespectively.RegexPattern/RoutePatterninstances and are located atself.pattern.regex(wasself.regex).url()and the newpath()returnURLPattern. So, no changes needed to support the new routing syntax.