On 7/10/07, Forest Bond <[EMAIL PROTECTED]> wrote: > All of this could be fixed by simply changing ModPythonRequest > (django/core/handlers/modpython.py) to use req.path_info instead of req.uri. > Is > there any reason not to do that (aside from breaking backwards compatibility)?
I'm certainly no expert in this area, but keep in mind that mod_python is just one available option for deploying Django. There would have to be some equivalent in the other situations, such as FastCGI, in order for this to be taken seriously. Above all, I think the intent here is consistency. It's hardly a Good Idea to have one way to lay out your URLs for mod_python and a different one for the rest. I'm not saying it's impossible to do (I don't know enough to say that), just that they all need to work the same way. So if mod_python ends up being the only one that supports this, I'd be very opposed to making changes for the mod_python case. -Gul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
