Is it 'correct' when installing Django with Apache to set the PythonPath variable to contain both your 'project' directory, ie where your Django apps live, _and_ the path to the actual application itself, it one level down from the 'project' directory? This is not what is done in the tutorial on the Django site, but other sites suggest it as a way to be able to reference other modules within an app without using the app name as part of the python path to the module. It seems to be the only way to make apps 'pluggable' as the Django docs seems to suggest they should be, ie movable to other projects with minimum fuss. The urls.py has a built in syntax for exactly this type of decoupling of app from project.
Any suggestions or comments on the correct that way this should be done? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
