After some googling I found the solution myself.
For each branch of the same project I can set the following directives
in my Apache configuration:
<Location "/someproject/">
SetHandler mod_python
PythonHandler django.core.handlers.modpython
PythonPath "sys.path+[r'/absolute/path/to/the/trunk']"
SetEnv DJANGO_SETTINGS_MODULE someproject.settings
PythonDebug On
PythonAutoReload On
PythonInterpreter someproject
</Location>
<Location "/someproject2/">
SetHandler mod_python
PythonHandler django.core.handlers.modpython
PythonPath "sys.path+[r'/absolute/path/to/the/somebranch']"
SetEnv DJANGO_SETTINGS_MODULE someproject.settings
PythonDebug On
PythonAutoReload On
PythonInterpreter someproject2
</Location>
I also symlink media directories respectively to someproject-media and
someproject2-media in Apache htdocs.
Anyway, thanks, Scott, for your help as well.
Regards,
Aidas Bendoraitis [aka Archatas]
PythonPath
"sys.path+[r'/Library/Subversion/general_src/branches/kulturprojekte']"
On 3/19/07, Aidas Bendoraitis <[EMAIL PROTECTED]> wrote:
> How can you import from a package if it is not under python path? Is
> there another way to do that than just to create a symlink in
> site-packages? PYTHON_PATH environment variable?
>
> The relation between someproject and someproject2 in my case is
> similar to django trunk and django per-object-permission branch. They
> are like one project at different statuses and at some point they'll
> need to be merged (at least some parts of them). Both someproject and
> someproject2 are self-contained projects. No other project uses any
> part of them.
>
> Regards,
> Aidas Bendoraitis [aka Archatas]
>
>
>
> On 3/19/07, ScottB <[EMAIL PROTECTED]> wrote:
> >
> > Hi Aidas.
> >
> > On Mar 19, 2:18 pm, "Aidas Bendoraitis" <[EMAIL PROTECTED]>
> > wrote:
> > > I have a symlink from trunk/someproject to site-packages/someproject
> > > on my machine.
> > >
> > > I need to launch the branched version of the project at the same time.
> > > So intuitively I create a symlink from branches/somebranch/someproject
> > > to site-packages/someproject2 to get it to the python path.
> >
> > Do your projects really need to be in site-packages? Are they normal
> > self-contained projects, or does something else import them?
> >
> > I'm thinking you could have:
> >
> > /home/me/dev/someproject/
> > /home/me/dev/someproject2/
> >
> > Then either use manage.py runserver for each one (with different
> > ports), or configure Apache/Lighty/whatever to access those two
> > projects under different urls. That way, both can run simultaneously.
> >
> > Scott
> >
> >
> > > >
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
