Sorry bout the unfinished second half of that last message, I was just thinking through type and I meant to delete it before posting.
On Jul 27, 4:16 pm, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > The other problem is that although with the better WSGI adapters > SCRIPT_NAME is provided correctly set for you automatically, in > mod_python one cannot actually deduce SCRIPT_NAME automatically with > the way the adapter works and so you push onto the user the need to > define the mount point manually a second time. I get that mod_python is a bit dumb, but my change isn't changing anything for mod_python users. It only changes the behaviour of the wsgi request handler. > What it comes down to is there are a few sides issues that really need > to be looked at at the same time and the simplistic change may not be > adequate to cover these or not result in the same behaviour on all > hosting solutions. Granted, the one thing I hadn't put too much consideration into is url `reverse` method. At the moment, it is totally decoupled from request, so it can't figure out SCRIPT_NAME. Perhaps request could get a SCRIPT_NAME aware reverse method (which would still work without it)? Are there any other issues I'm missing? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
