Got it! I've been actively using GNU/Linux since mid-90's and it's always the same issue... permissions...
I got the OTHER_DJANGO_PATH pointing to a root-only directory, so apache (or mod_python), wisely, ignored it and, so, went on until site- packages gloriously appeared. I just can't believe I keep falling into these every now and then. Thanks! you made feel confident about the pythonpath so I started looking elsewhere (though I though I had that permission error already nailed down...) :-) Pablo On Dec 8, 12:27 pm, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > On Dec 8, 10:15 pm, Pablo Ruiz Múzquiz <[EMAIL PROTECTED]> wrote: > > > Hmm. That is exactly what I meant with "No matter what I do with > > Apache's PythonPath". > > I have that same configuration you posted and /admin (and other stuff) > > won't work (most certainly because of the django version mismatch) > > > The two errrors are "no module named urls" and "Viewdoesnotexist .. > > could not impot login. cannot import name validators" > > > Thanks anyway, I'll keep trying! > > Post your actual configuration then. > > There are various subtleties in using mod_python and since you haven't > posted your actual configuration, you could be doing something obvious > wrong, but we cannot tell. Saying you have the same as other poster is > not enough as what they posted doesn't explain everything. > > > Pablo > > > On Dec 7, 8:08 pm, Adi Sieker <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > On 07.12.2008, at 16:56, Pablo Ruiz Múzquiz wrote: > > > > > Hi all, > > > > > I'm afraid I googled and googled with no success. Django official docs > > > > or my django book weren't of any help either. > > > > > I've got a "legacy" django project which was developed using 0.97svn a > > > > year ago and a brand new SVN one, sharing the same server. > > > > > Django 097 lives at /srv/whatever/django097/django while Django SVN at > > > > the usual site-packages location. > > > > > No matter what I do with Apache's PythonPath, the virtualhost > > > > referring > > > > to the old project will load the SVN version and, thus, /admin and > > > > some > > > > template handling will fail to load. > > > > > Any clues? Thanks in advance, > > > > I'm doing that on one of my domains with mod_python and it's working > > > just fine. > > > Here is my relevant apache config. > > > > <VirtualHost *:80> > > > ServerName vhost1 > > > <LocationMatch /(?!favicon\.ico)> > > > SetHandler python-program > > > PythonHandler django.core.handlers.modpython > > > SetEnv DJANGO_SETTINGS_MODULE project.settings > > > PythonPath "['<PATH TO DJANGO>', \ > > > '<PATH TO DJANGO PROJECT PARENT DIR>', \ > > > '<PATH TO DJANGO PROJECT>'] + sys.path" > > > </LocationMatch> > > > </VirtualHost> > > > > in this VirtualHost <PATH TO DJANGO> points to a pre newforms admin > > > version of django and then a duplicate of this VirtualHost where the > > > <PATH TO DJANGO> points to a trunk version of django. > > > The _really_ important part is that sys.path comes after the version > > > you want to use for this host. > > > Since sys.path will include your site.packages it'll find the trunk > > > version first. > > > > adi > > > > -- > > > Adi J. Sieker mobile: +49 - 178 - 88 5 88 13 > > > Freelance developer skype: adijsieker > > > SAP-Consultant web: http://www.sieker.info/profile > > > openbc:https://www.openbc.com/hp/ > > > AdiJoerg_Sieker/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
