[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: python-debconf, Byte compilation and other questions



Luca - De Whiskey's - De Vitis writes:
> 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.

And/or take a look at dh_python, which does all this for "free"...



Reply to: