Pinax hijacks PYTHONPATH

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install django-hotclub
2. Try to use different app with same name as Pinax app
3. fail

What is the expected output? What do you see instead?
I should be able to easily override any package in Pinax with my own. Instead, 
the default 
manage.py forces you to use Pinax apps by pushing them to the front of sys.path

What version of the product are you using? On what operating system?
trunk

Please provide any additional information below.

In general it should be easier to deploy and customize Pinax in a separate 
project. Fixing this 
issue would go a long way in that direction

Original issue reported on code.google.com by sgt.hu...@gmail.com on 15 Sep 2008 at 6:31

[GoogleCodeExporter]

This is a bit of unfortunate FAD.
At the heart of the problem here are issues with shared hosting which have 
old/bad versions of the site-
packages apps and some name collisions with the apps in /apps/.

Is it really so hard to use the django/bin/django-admin.py ?
what would you propose we do for these shared host situations?

Personally I would like to go over to a virtual_env setup.

Original comment by doug.nap...@gmail.com on 16 Sep 2008 at 12:05

[GoogleCodeExporter]

Yeah, I understand there may not be an easy fix for this, but I was chatting 
with brosner today and he mentioned 
I should file a bug for it.

I'm in the middle of moving all my sites to virtualenv/mod_wsgi which will 
provide an easy work-around 
although it may not be accessible for everyone.

Original comment by sgt.hu...@gmail.com on 16 Sep 2008 at 1:39

[GoogleCodeExporter]

We have since moved away from svn:externals and thus ultimately fixing the 
issue here. Closing.

Original comment by bros...@gmail.com on 5 Feb 2009 at 3:32

• Changed state: Fixed