Hi, On Fri, Jan 18, 2008 at 10:30:53AM +0530, Kenneth Gonsalves wrote: > On 18-Jan-08, at 12:20 AM, LRP wrote: > > I'm still having a problem since my shell can't seem to find django- > > admin.py. I know it's there; found it in /usr/share/python-support/ > > python-django/django/bin. > > this will not be on your path - and why debian packagers created that > weird directory is beyond me
Well the tone here is degrading rapidly.
Debian supports multiple Python versions simultaneously, and every Python module
installed via the package manager works with all of the installed Python
versions. One of the ways it does this is with the "python-support" system.
Here, Python modules are installed in /usr/share/python-support/[package name].
In this case, the package name is python-django, and the "django" directory is
simply the source tree from the django release. The modules are hooked into
each Python's site-packages directory via .pth files.
It's actually pretty elegant, I've found, and the usual problems associated with
multiple interpreter versions just don't exist on Debian machines (which is
certainly not the case on the RHEL server I've dealt with).
> > Then there's Kenneth Gonzales. All I can say is, "hey dude, that's not
> > very friendly."
>
> well, I was one of the people who told you *not* to rely on debian's
> apt-get for installing django - django is developing too fast for
> package managers to keep up with. So, if, inspite of everything you
> want to use django, please install an uptodate version without apt-get.
You have to admit that, in the vast majority of open-source projects, it is not
common for end users to run software straight from svn.
Moreover, as a user, I don't trust upstream developers to tell me how to put
software on my Debian/Ubuntu machine. They are almost always wrong because they
don't know Debian. On the other hand, I know Debian really well, so I have
pretty good instinct about these sorts of things.
It's a tricky business at first, though, figuring out who to ignore, and when :)
(That said, there is a good point here: if you don't follow upstream's
installation docs, you can't expect upstream to support your installation.)
Now, in this case, I do run straight from svn, but only because I've found that
django makes a good exception to the norm. The development version is
reasonably stable, bugs get fixed reasonably quickly, and the API is still
changing in a way that I'd rather not be too far behind on.
In fact, if I only use the machine for development, I keep django in
~/lib/python/django. For production, I put it in
/usr/local/lib/python${version}/site-packages/django. And I understand that it
is up to me to maintain my PYTHONPATH (which my .bashrc does wonderfully).
-Forest
--
Forest Bond
http://www.alittletooquiet.net
signature.asc
Description: Digital signature
