Re: Compiled bytecode files location

2009-02-19 Thread Ben Finney
Josselin Mouette j...@debian.org writes: Le mercredi 18 février 2009 à 13:33 +1100, Ben Finney a écrit : I saw no response to Message-ID: 87skwceynw@benfinney.id.au on this forum, but would love to be convinced this will be fixed. This is probably the last remaining issue keeping me

Re: Compiled bytecode files location

2009-02-19 Thread Josselin Mouette
Le jeudi 19 février 2009 à 18:06 -0500, Guy Hulbert a écrit : So *.py ( and *.pyc, iirc ) should be under /usr/share. Yes: http://www.network-theory.co.uk/docs/pytut/CompiledPythonfiles.html The contents of the ‘spam.pyc’ file are platform independent, so a Python module

Re: Compiled bytecode files location (was: Python related changes for unstable/squeeze)

2009-02-18 Thread Josselin Mouette
Le mercredi 18 février 2009 à 13:33 +1100, Ben Finney a écrit : I saw no response to Message-ID: 87skwceynw@benfinney.id.au on this forum, but would love to be convinced this will be fixed. This is probably the last remaining issue keeping me with ‘python-central’ for my packages. As I

Compiled bytecode files location (was: Python related changes for unstable/squeeze)

2009-02-17 Thread Ben Finney
Piotr Ożarowski pi...@debian.org writes: Sure, pysupport is not perfect. Using /var/ for bytecompiled stuff is probably the worst of it's bugs, but maintainer is aware of this and will most probably fix it during the move to /usr/{share,lib}/py{,3}shared - and I have a reasons to believe that