> About the url convention We're not changing anything about the URL conventions, we're changing the oath syntax. Django tends to use a trailing slash style by convention. This proposal wouldn't change that in any way.
> The only technical reason I see for enforcing the starting slash The leading slash in the syntax is open to discussion, however I'm very strongly in favor due to two points: * It is a strong and consistent visual indicator. * Doing so would mean that Django and Flask share exactly the same routing syntax. (Flask enforces a leading slash) I think there are *very* strong reasons to have a single consistent URL syntax used across the two most popular Python web frameworks. This is a new syntax, and the capture groups have changed substantially, so I think it's acceptable that it also doesn't happen to echo the regex style wrt this particular aspect. > The question about the old routing system is about the plan to build on top the old one. There's nothing to stop a current or later proposal for redesigning the URL system in order to provide for non-path based routing. That's a different conversation. Nor is there anything to stop either an internal refactoring, or an alternate proposal for how to implement the described syntax. Design proposals or PRs welcome. -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/4011b577-4ce8-4f1f-8c04-027d5b9cc8b5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
