I have one comment about the part that says: """Make sure that you specify the correct SCRIPT_NAME which should be the name of your Pylons Project and that your PythonPath points to the correct directory."""
SCRIPT_NAME actually should be the location under which Apache executes the WSGI application. So if the url of the root of your WSGI application is http://myhost/whatever SCRIPT_NAME should be /whatever, no matter what the pylons project is or the directory it's stored in. Usually (at least in my tests) if you setup mod_python + ModPythonGateway in a <Location> Apache directive, there's no need of "PythonOption SCRIPT_NAME ..." because Apache itself will corectly generate SCRIPT_NAME, and mod_python and ModPythonGateway will use that. On the other hand, if ModPythonGateway is used in a <Directory> directive or in .htaccess then SCRIPT_NAME is required because Apache seems to not be able to generate the correct SCRIPT_NAME. And then, there's another mod_python WSGI server implementation that works better in the <Directory> case, and worse in the <Location> case, but I've not had that much experience with it yet (and don't remember the url). +1 on saving ModPythonGateway as mod_python.wsgi a WSGI server should really be a part of mod_python but the mod_python developers seem to be stubborn about it (and incidentally the it's the same with python's scgi module and developers). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss -~----------~----~----~----~------~----~------~--~---
