On Wed, May 28, 2014 at 2:51 PM, Marc Tamlyn <[email protected]> wrote:
> I'm not saying any of this is not currently possible - it is. But I'd > prefer to introduce a stable, robust API and then look at exact > implementations of format. > > I completely agree -- rather than pick something from a bunch of good options, I'd rather us introduce an API to make resolution pluggable and customizable (and then, maybe, choose a good default that's easier than regexes). I've done some looking into this. It's possible, but going to be pretty difficult: resolution is one of the last great superglobals hanging around Django, and it's very tightly coupled into the core http/wsgi server. It'd take quite a bit of refactoring and cleaning to make this happen, unfortunately. I'm all for it, but it's not going to be easy. Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAK8PqJFvwXw65BZ7jQEgGbiigv5AHDXsGd-4rDXUXBQq%2Bztx5Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
