Personally I haven't found the need for this, since I don't lay things out like that.
However, using the new-ish urlpattern url() notation would be the go here. Just bung a new kwarg on url.__init__() with a default of something like None, ALL or *, that would optionally accept values like GET, POST, HEAD, etc. On Oct 2, 10:53 pm, "Marty Alchin" <[EMAIL PROTECTED]> wrote: > On 10/2/07, Marty Alchin <[EMAIL PROTECTED]> wrote: > > > That said, I think there are probably others out there like you who > > would want this, and there's actually nothing stopping you from > > releasing it as a separate app, or even a snippet. > > Well, looks like I misspoke. It seems the URL resolver is only given > the path, as opposed to the whole request object, so it would require > a bit more hacking than I originally thought. It might still be > possible without changing any Django internals, but you'd have to > touch more than you should, and it wouldn't be pretty. I wouldn't > recommend it, so consider that whole idea withdrawn. Sorry about not > looking at the code before I typed. > > -Gul --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
