On Apr 14, 2010, at 04:14 PM, Jakub Wilk wrote:
>python-central seems to have some (at least rudimentary) support for
>3.X.
>
>I was told that python-support does not support 3.X (see bug #573560).
I am hoping that none will be necessary. PEP 3147 is very close to acceptance
and merging into the py3k upstream trunk, perhaps as soon as this Friday. Of
course that means that symlink farms will no longer be necessary starting with
Python 3.2, but I would happily back port the essential parts of the patch to
3.1 or even 2.6 and 2.7 if folks here want it, and think it will help. I do
not think it would be difficult, and if it means simplifying Python
installations on Debian, I think it would be a big win.
(For backward compatibility, Pythons < 3.2 would need a -Xcachedir flag to
enable PEP 3147 style pyc files, as specified in the PEP. This means it would
be enabled by default only for system installed Python packages, but that
would still allow us to get rid of the symlink farm for apt packages.)
>>- how to do that properly? simply build with python3.x and then ship
>>the /usr/lib/python3.x/<mod> dir?
>
>s|python3.x|python3.x/dist-packages|
>
>However, that would be wrong for pure-Python modules. If root imports
>such a module, it will be byte-compiled, but then *.pyc won't be removed
>on purge.
>
>On the other hand, almost the same can be said about modules for 2.X
>(even when managed by python-{central,support}): if root imports one
>with -O, .pyo will be created but never removed.
Isn't compileall used to create the pyc files? I think all pyc and pyo files
should be placed on the system by the time the package is installed.
-Barry
signature.asc
Description: PGP signature
