Hi, On Mon, Jan 14, 2008 at 04:08:57PM +0100, Raphael Hertzog wrote: > On Mon, 14 Jan 2008, Andrea Gasparini wrote: > > I know that this is Debian, and you go against _debian_ bugs. > > But I guess that you could "mainly" support django for 2.4 python version, > > and why don't try to 'partially' support also other versions? > > At least we could minimize diversion between distributions. > > Well, there's some support for other python versions and Debian will > switch to python 2.5 too. It's just that if you want to use a non-standard > version, you have to expect some manual changes because the policy of > Debian is to support officially only one python version at a time.
I think the point here is to make it any harder to use a different python version but I see your point. > > > > Why can't you simply edit the manage.py script to match the python > > > version that you'd like to use instead of requiring the script to > > > hardcode any python version that might be currently used? > > > > Because i'm not the only that sees that issue. > > Of course, we can edit manage.py... but why, if it can be done > > automatically? > > It's not automatic since you have to change the invocation of django-admin > to give a special interpreter. :) > > And if you're doing something explicit like that you might as well just > edit the generated file. Indeed, thinking about this I am more inclined to think about it as an upstream "bug" than a distribution one, how does this sound? > > > > Furthermore, if manage.py hardcodes a python version, the end-result > > > might be that the Django application stops working when the given python > > > version is dropped from Debian while using #!/usr/bin/python makes it > > > work whatever the current version is. > > > > You're right about that. > > But, if someone use 'normally' django-admin, calling it directly, it ends > > in a "/usr/bin/python" shebang, that should be fine. > > How do you expect django-admin to know that it has been called by python > or by python2.4 (when they are the same in Debian currently) ? Would it be necessary to know if django-admin is called by the standard interpreter? Anyway, how about something like this? os.path.join(os.path.dirname(sys.executable), os.readlink(sys.executable)) thanks, filippo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
