Re: Installation - symlink vs. python setup.py install

2007-12-05 Thread Graham Dumpleton
On 10.5 with a virgin Python 2.5 installation there is no: /System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/ site-packages If you have it then something has wrongly created it and you probably should delete the whole directory in case it causes problems. The Python 2.3 ins

Re: Installation - symlink vs. python setup.py install

2007-12-05 Thread Graham Dumpleton
Okay, I had a part brain fade there. Was confusing /Library/Frameworks/ Python with /Library/Python. The /Library/Frameworks/Python is what MacPorts uses. Also looks like Python 2.5 on Mac OS X 10.5 sets up sys.path differently, ie., uses shorter /Library/Python/2.5/sites-packages instead of long

Re: Installation - symlink vs. python setup.py install

2007-12-05 Thread Greig Rapley
$ sudo port installed does not include python in the list returned, so I assume I am using the OS version. $ which python /usr/bin/python and, $ python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()" /Library/Python/2.5/site-packages I have been symlinking into /Li

Re: Installation - symlink vs. python setup.py install

2007-12-04 Thread Graham Dumpleton
BTW, that it is looking in: /Library/Python/2.5/site-packages suggests your mod_python is using MacPorts Python. Where were you actually symlinking in to? If you were symlinking into /System/Library/Frameworks/Python/Current/ lib/site-packages it wouldn't find it as it doesn't look there. C

Re: Installation - symlink vs. python setup.py install

2007-12-04 Thread Graham Dumpleton
On Dec 5, 10:29 am, Greig Rapley <[EMAIL PROTECTED]> wrote: > Unfortunately that hasn't worked. I even tried chown'ing the entire > tree beneath django-trunk, and the symlink itself, to www:www. Still > mod_python says that it cannot import django.core.handlers.modpython. > I have gone through yo

Re: Installation - symlink vs. python setup.py install

2007-12-04 Thread Greig Rapley
Unfortunately that hasn't worked. I even tried chown'ing the entire tree beneath django-trunk, and the symlink itself, to www:www. Still mod_python says that it cannot import django.core.handlers.modpython. I have gone through your mod_python mptest exercise again and everything works fine. Then

Re: Installation - symlink vs. python setup.py install

2007-12-03 Thread Graham Dumpleton
Apache generally runs as a special user. This user must have read access to those Django modules you have symlinked into the Python site- packages directory. Thus if the files are not readable to others, or any of the directories from the root right down to where the Django software is actually in

Re: Installation - symlink vs. python setup.py install

2007-12-03 Thread Greig Rapley
Actually, I have just rerun "python setup.py install" to get my installation working again and noticed the running install_egg_info that happens last. Might this have something to do with my problems when using a symlink instead ? On Dec 3, 6:17 pm, Greig Rapley <[EMAIL PROTECTED]> wrote: > Hi,

Installation - symlink vs. python setup.py install

2007-12-03 Thread Greig Rapley
Hi, I have django (trunk) installed on MacOSX 10.5 using mod_python and it all works fine when I use python setup.py install to actually install the files retrieved via subversion. However if I follow the installation instructions to use a symlink to my SITE-PACKAGES directory I get the followin