> This is at best a wishlist report : Yes, it would be so, i missed the tag, sorry.
> 1/ since django-admin is in /usr/bin/ it's meant to be directly called > (without any explicit interpreter) It could be done to rely on a specific version of python, or because, as you said below, i changed the standard python version. > 2/ django is supported for the current python version mainly (current > being defined as the version corresponding to the /usr/bin/python > provided by the official "python" package) You're right, but look that in ubuntu the official python package is 2.5-something. 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. And, why doesn't make something that increase the support toward newer versions of python? I think it doesn't hurts, and it's already done. (the patch in ubuntu launchpad could be applied easily also in debian... ) > 3/ your machine is not a "standard" Debian machine since you manually > changed the /usr/bin/python symlink to point to python2.5 Yes, it's not a 'standard' Debian, cause it's a 'standard' Ubuntu machine. ;) But you can repeat theese steps with 2.4 and 2.5 exchanged. ( "python2.5 /usr/bin/django-admin ..." that will ends in calling python2.4 in a 'standard' Debian machine) > 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? > 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. Besides, if someone else use django-admin with a specific python version (as me ;) ), I guess that he want to rely on that specific version, and so manage.py should maintain the right version. Hope I don't make too much mess. :D Thanks. -- -gaspa- ----------------------------------------------- -------- https://launchpad.net/~gaspa --------- ------ HomePage: iogaspa.altervista.org ------- -Il lunedi'dell'arrampicatore: www.lunedi.org - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
