It doesn't really matter where it is, as long as it's on the pythonpath (eg. "import django" works). Putting it in site-packages is just a bit cleaner, as that is a standard place for common-use python packages.
You still need to be able to set the pythonpath for your execution environment, though. This means PythonPath for mod_python and PYTHONPATH for anything shell based. If you can, put it in site-packages (even if it's just a symlink). It's already on the path, and will Just-Work(tm). ~Chris El s�b, 06-10-2007 a las 09:47 +0200, horace escribi�: > hello, > > wouldn't it simply be possible to put all the py files of django into > a directory and use "import" in your project instead of installing > anything? django looks really nice but most webhosters don't allow to > install it. :) > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---