First, a little background. I'm a Windows user *shrugs*. Historically,
we've been missing love from the OS community, and one of those is the
ability to bootstrap Apache for a project on Windows. I believe it is
common practice for Windows developers, or at least the uninitiated
Windows developers such as myself, to maintain a single Apache
installation and then configuring `VirtualHost` for each development
project.
My troubles with WSGIPythonPath come from having to use virtualenv. I
have envoronment.pth set in my environment's root, specifying paths to
the required packages. Currently, since WSGIPythonPath can be
specified in the server config context only, I believe I would be
loosing control over managing different package versions across my
projects:
Project_A uses Django SVN trunk, Project_B uses Django 1.1.
...
In my Apache conf I have:
WSGIPythonPath "C:/~/Project_A;C:/~/Project_B"
...
Project_B will now be using the SVN trunk version of django
...because Project_A/src/Django is located in sys.path before
Porject_B/src/Django.
Is there any *better* way to rectify this by using mod_wsgi or apache
conf gymnastics without having to resort to configuring an Apache
instance for each project or changing my project's code?
(In case you noticed and would like to know, buildout isn't used
because a lot of the recipes do not work for Windows, including
djangorecipe; I could write custom wsgi scripts that use the `site`
module, but I like to keep my applications unaware of any underlying
deployment difficulties.)
--
You received this message because you are subscribed to the Google Groups
"modwsgi" 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/modwsgi?hl=en.
