Re: question on packaging of python applications
On Thu, 2 Nov 2000, Bastian Kleineidam wrote: > >I recently created a debian file for my project (see http://subterfugue.org), > >and discovered just now why including .pyc and .pyo files directly doesn't > >work optimally. > Where is the problem? Python bytecode should be platform > independent! So it is safe to include .pyc and .pyo files. There is no > need to compile them at configure time. Well, there might be a problem with Python version. While 99% of all Python source code will work with Python 1.5.2, 1.6 and 2.0, the bytecode format has changed, and will probably continue to change when 2.1 comes along.
Re: question on packaging of python applications
Hi, it seems there are some points to _not_ precompile Python files. - packages get bigger (they get substantially bigger, more than twice the size if they have lots of .py files) - compatibility: I found the official wrapup Third party extensions built for Python 1.5.x or 1.6 cannot be used with Python 2.0; these extensions will have to be rebuilt for Python 2.0. Python bytecode files (*.pyc and *.pyo) are not compatible between releases. Ok, so if you use the distutils, use python setup.py install --no-compile --root=`pwd`/debian/tmp in your rules file and compile your .py files in the postinst script. BTW: is there yet a .deb package for the Distutils? If not, I will package it (when I am a Debian Developer, I am still in the queue). Greetings, Bastian
Re: question on packaging of python applications
Bastian Kleineidam <[EMAIL PROTECTED]> writes: > BTW: is there yet a .deb package for the Distutils? If not, I will package > it (when I am a Debian Developer, I am still in the queue). It is already in woody and packaged by Matthias Klose. It is named python-distutils. -- Jérôme Marant <[EMAIL PROTECTED]> http://jerome.marant.free.fr
