Re: Python module packages that don't bytecompile on installation?
On Sat, Nov 2, 2019 at 6:04 PM Matthias Klose wrote:
> At this point I'd ignore any Python2 related package, and concentrate on Python3
> stuff only.
Yes, I was referring only to python3-* module packages.
> Byte compilation is an optimization, speeding up a program start if
> byte-compiled files are ready. Packages are smaller without bc, take a bit
> longer to install. I think nobody is asking the question if .py files should be
> dropped in favor of .pyc files.
As I understand it, the .pyc files are interpreter version specific
and doing a transition for each major Python update was deemed to be
too much work, so instead we offload building the .pyc files onto
user's systems.
> I'd say, there are currently more pressing issues than that, like the Python2
> removal, or the introduction of Python 3.8. 3.8 also offers a central directory
> for bc files, so that's maybe another thing to look at, but not a priority now
> from my point of view.
Agreed re Python 2 etc. Eventually switching to using a central
directory in /var would be nice, right now the .pyc files are dumped
cruftily into /usr subdirs.
--
bye,
pabs
https://wiki.debian.org/PaulWise
https://bonedaddy.net/pabs3/
Reply to: