bytecompilation and default python version
Hello, I have two small questions regarding byte-compiling python modules in the maintainer scripts of python library packages. 1. If a package installs modules under /usr/lib/site-python, should the postins script produce .pyc files ? .pyo files ? 2. If the answer to 1. is 'yes', the current common practise is to use the compileall.py script which lives in /usr/lib/python2.X, which means that the packages have to be changed if the default python version changes. I think things would be nicer and cleaner if this script was provided in the python package (maybe as a symbolic link, or an executable such as /usr/bin/python-compileall) so that the packages can avoid depending on a versioned python version when they are version independent. Thanks for your feedback. -- Alexandre Fayolle LOGILAB, Paris (France). signature.asc Description: Digital signature
Re: python2.3/python2.4/python packages
On Mon, 2006-02-20 at 20:37 +0100, Matthias Klose wrote: Donovan Baarda writes: [...] In the mean time, another alternative is to point your apt/sources.list at an Ubuntu archive and see if you can upgrade python from there... ugh, I would not try that ... you cannot differentiate between python and non-python things ... I never said it would be easy :-) You can kind of do this using a combination of /etc/apt/preferences and judicious use of aptitude. Cunning preferences-fu can favour most packages in Debian, except python* packages from Ubuntu. You can then use aptitude to fine-tune pick and choose which versions you want to install. This will probably reveal nasty dependencies of the python packages on bucketloads of other Ubuntu libs etc, but you might get lucky... -- Donovan Baarda [EMAIL PROTECTED] http://minkirri.apana.org.au/~abo/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bytecompilation and default python version
Alexandre Fayolle writes: Hello, I have two small questions regarding byte-compiling python modules in the maintainer scripts of python library packages. 1. If a package installs modules under /usr/lib/site-python, should the postins script produce .pyc files ? .pyo files ? yes. 2. If the answer to 1. is 'yes', the current common practise is to use the compileall.py script which lives in /usr/lib/python2.X, which means that the packages have to be changed if the default python version changes. I think things would be nicer and cleaner if this script was provided in the python package (maybe as a symbolic link, or an executable such as /usr/bin/python-compileall) so that the packages can avoid depending on a versioned python version when they are version independent. the next python package will have such a script, and will recompile these files on a python upgrade as well. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
