Okay, I guess I can live with that. Maybe, if I can write a patch implementing this in a completely backwards-compatible way, I'll propose it again for a later version (earlier in the release cycle).
Though I disagree with your characterization of it as "what looks like regular expressions with names." It would be compiled down to regular expressions, yes, but it's not really intended to be just a wrapper over regular expressions. (I wrote one of those in about three minutes.) Maybe if you looked at Werkzeug's routing source code, you'd see what I mean. I personally like it because it's cleaner, both using it from the front end and in the source. -- LeafStorm On Oct 17, 7:00 pm, James Bennett <ubernost...@gmail.com> wrote: > On Sat, Oct 17, 2009 at 10:29 AM, Leaf <leafstormr...@gmail.com> wrote: > > Sorry to propose this right up against the voting deadline for 1.2 > > features, but it's one of the things that has always bugged me about > > Django and I would really like to see this in 1.2. > > -1. > > Replacing regular expressions with... well, what looks like regular > expressions with names doesn't make much sense, and even if it did > we're not going to change a major component like this in the middle of > a stable release line. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
