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 modul

Re: Compiled bytecode files location

2009-02-19 Thread Guy Hulbert
On Fri, 2009-20-02 at 09:27 +1100, Ben Finney wrote: > I think ‘/usr/lib/foo/’ is better than ‘/var/lib/foo/’ for program > libraries such as *.py and *.pyc, so to that extent it's a significant > improvement. Why do you not follow FHS ? /usr/lib/fooarchitecture dependent /usr

Re: Compiled bytecode files location

2009-02-19 Thread Ben Finney
Josselin Mouette 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 with > >

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