Re: Compiled bytecode files location
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 with ‘python-central’ for my packages. As I already said, there is no compelling reason to stay in /var, Okay, I didn't see that when I looked back in the list archive. and this can be changed without too much breakage - I just couldn’t do that right before the lenny release. Sure, I was only hoping for discussion at that time, not immediate implementation of changes. I just proposed /usr/lib/pymodules/pythonX.Y instead. Do you think that location is suitable? 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. As for which directory names should be used under that hierarchy, I'm currently neutral on most proposed systems I've seen. I'm not educated enough on the issue of separation of these files to have an informed opinion yet. -- \ “Yesterday I saw a subliminal advertising executive for just a | `\ second.” —Steven Wright | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Compiled bytecode files location
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 directory can be shared by machines of different architectures. .py files are shipped in /usr/share, but the symlink farm has to live in /usr/lib because it also includes symlinks to binary .so files. -- .''`. Debian 5.0 Lenny has been released! : :' : `. `' Last night, Darth Vader came down from planet Vulcan and told `-me that if you don't install Lenny, he'd melt your brain. signature.asc Description: Ceci est une partie de message numériquement signée
Re: Compiled bytecode files location (was: Python related changes for unstable/squeeze)
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 already said, there is no compelling reason to stay in /var, and this can be changed without too much breakage - I just couldn’t do that right before the lenny release. I just proposed /usr/lib/pymodules/pythonX.Y instead. Do you think that location is suitable? -- .''`. Debian 5.0 Lenny has been released! : :' : `. `' Last night, Darth Vader came down from planet Vulcan and told `-me that if you don't install Lenny, he'd melt your brain. signature.asc Description: Ceci est une partie de message numériquement signée
Compiled bytecode files location (was: Python related changes for unstable/squeeze)
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
he'll use this path if you decide to use /usr/lib/py{3,}shared (I'll
convince him, leave it to me ;)
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.
--
\ “He may look like an idiot and talk like an idiot but don't let |
`\ that fool you. He really is an idiot.” —Groucho Marx |
_o__) |
Ben Finney
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
