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
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
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
> >
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
Piotr Ożarowski 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
> he'll use
5 matches
Mail list logo
