Wanted to add my support for this. Personally I'd be totally in favour of considering something along these lines for core, once there's a fully proven design.
The capture syntax is: * Far simpler. * Meets pretty much every single real-world case I ever see. * Gives us type coercion. * Also able to support regex fragments if needed. Eg see http://stackoverflow.com/questions/5870188/does-flask-support-regular-expressions-in-its-url-routing Given that we could continue to keep the existing style around as well, this is an area where I'd be happy to see Django take a step forward. Sticking with the path->existing regex mapping implementation sounds like the best tack, at least initially, rather than getting bogged down in API discussions around how we'd tackle a routing API if we wanted to support non-path routing. Cheers, Tom -- 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/9a0ee2a3-37bc-4b4d-83e3-a2a1b6cf34e5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
