On May 23, 3:16 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> 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.
James, thanks for the succinct explanation. That confirms what I
thought (in a slightly uncertain way) was happening.
> 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.
I have actually edited my Python path already - that's how I got the
development version working - so perhaps there's something else not
right? In any case, moving 0.96 onto the Python path is not really an
option for me, as I already have a working copy of 0.95 sitting there.
I was actually trying to set up an alternate instance of Django so I
could test its compatibility with my code, before upgrading the copy
of Django that runs behind my main server. I don't want the
embarrassment of upgrading and ending up with a broken site. The fact
that I can get the dev version working in the alternate directory, but
not the 0.96 version makes me worry that it's something more than just
the Python path.
By the way, my site *does* break under the dev version - I have a
couple of FloatFields in there - but as soon as I changed them it
worked fine. So what started as a cautious test of my code's
compatibility with the latest version of Django, has now made me worry
about my ability to install an official Django release! Previously
I've worked with either dev releases (using svn), or pre-installed
official releases (on WebFaction), so I haven't had to face this
before.
Thomas
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
