Hi Tom, I'm not sure how the timing will work out, but an option could be to target this for inclusion in Django 2.0 but make the necessary fixes in Django 1.11 to allow this to exist as a third-party app in the meantime. That would allow it some time to get some real world usage and undergo more rapid iteration before it's included in Django.
I thought of one thing for the implementation checklist: the simplify_regex() function in admindocs should probably be a method of the URLPattern class. https://github.com/django/django/blob/979ea95608176e9c88678fd4d8a096c29654b5f3/django/contrib/admindocs/views.py#L432-L448 You can list me as the DEP shepherd if needed. On Thursday, October 6, 2016 at 8:02:07 AM UTC-4, Florian Apolloner wrote: > > > > 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/d5af56e1-20ea-40b7-9b60-c29c92ce12e8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
