On Thursday, October 6, 2016 at 1:30:38 PM UTC+2, MMeent wrote:
>
> It would shadow the stdlib os.path, albeit not as a library, but as a
> function.
>
I do not think that os.path will usually interfer with url routing, so I
don't take that as an argument. In the end, path is perfectly suitable,
since we are actually matching on the path and might (?) allow other
functions like subdomain() in the future. It would really be interesting to
end up with something like:
urlpatterns = [
subdomain('<user>') + path('/<page:int>/')
]
or similar
urlpatterns = [
subdomain('<user>,
path('/<page:int>/'),
…more paths for that subdomaiin
)
]
Cheers,
Florian
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/91abf0bf-8e90-4f76-af27-f68ce8157964%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
