On Fri, Apr 18, 2003 at 10:02:39AM +0200, Tim Dijkstra wrote: > 1) Should I ship .py or .pyc or both in the package. Byte-compile at > install time? Ask user what to do? > Ok, just saw a few other messages on this, my conclusion: > Byte-compile at install time > But how do I force the .py to get re-bytecompiled when a newer python > becomes the default? With a depends python < X.Y? Seems a waste of band > with, to download a new package only for its postinst run...
A quick reply is to ship .py, compile them at configure time and remove them at remove (not purge) time. Take a look to other python package: most of them use this behaviour. > 2) I would like to use the debconf-module, but it seems there is no > python priority:required, so is this module worthless? Please, be careful using debconf: you'd better read the "best packaging practice"[1] manual before using it. Then, I think you won't need a python-debconf. Use Debconf from the maintainer scripts (which you'd better to write in sh). > 3) The program is pure python code, so I guess it can be arch:all if I > ship only .py files, but are .pyc files also arch-independent? .pyc files are architecture independent. Perheps you've to read the python packaging policy file:///usr/share/doc/python/python-policy.txt.gz (that is shipped with the "python" package). ciao, [1] developers-reference package. -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][-A-Za-z]*[iy]'?s$ | as fine or rude sentences have Infinite loop: see `Loop, infinite'. | something in common: they Loop, infinite: see `Infinite loop'. | don't depend on the language.
