Re: Python versions and bytecode

2002-03-06 Thread Anthony Towns
On Thu, Mar 07, 2002 at 10:49:48AM +1100, Donovan Baarda wrote: > On Wed, Mar 06, 2002 at 10:38:22AM +0100, Josselin Mouette wrote: > Currently, you have the following options; > 3) Use "Depends: python (>=2.1)", and tell everyone they must run > "dpkg-reconfigure " after every default python upgra

Re: Python versions and bytecode

2002-03-06 Thread Donovan Baarda
On Wed, Mar 06, 2002 at 10:38:22AM +0100, Josselin Mouette wrote: > le mer 06-03-2002 ? 01:33, dman a ?crit : > > > | as I'm currently packaging solarwolf, I have a question about python > > | bytecode. I have put the .py files used by the game in > > | /usr/lib/games/solarwolf/ and I compile them

Re: Python versions and bytecode

2002-03-06 Thread Neil Schemenauer
dman wrote: > No. The bytecodes change when the developers feel like it (more or > less). That interface is not constant between even "minor" version > changes. Not quite true. Bytecode stays compatible between micro (i.e. bugfix) releases. Neil

Re: Python versions and bytecode

2002-03-06 Thread Josselin Mouette
le mer 06-03-2002 à 01:33, dman a écrit : > | as I'm currently packaging solarwolf, I have a question about python > | bytecode. I have put the .py files used by the game in > | /usr/lib/games/solarwolf/ and I compile them in postinst with > | compileall.py. The question is : will the generated .p