On 5/23/07, Thomas Ashelford <[EMAIL PROTECTED]> wrote: > I'm hoping that setup.py is just a convenience file that does > something I can do manually (I'm a python newbie, so when I took a > look inside I was a bit bamboozled. I could probably figure it out > given a spare hour or two!)
In order for Python to be able to use some bit of code -- in this case, Django -- that bit of code has to be in a directory that's on the "Python path"; that's a list of directories Python looks into whenever you have an 'import' statement. The job of setup.py is to automatically place a new Python-based application on the Python path so that Python can import code from it, though this is really provided as a convenience. The "manual" option is to either copy the "django" directory containing all of Django's code into a directory that's on the Python path, or to edit the Python path to include the directory Django is in. Editing the Python path varies across operating systems, so you may want to simply copy Django over to somewhere on the path. To find out which directories are on your Python path (and, therefore, where you could put Django so Python can find it), do the following in a Python interpreter: >>> import sys >>> print sys.path This will list all the locations currently on your Python path. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
