Re: Bytecode compilation
Dave Swegen <dswegen@software.plasmon.com> wrote:
> Not having really followed the discussion, and being faaar too bone-idle
> to actually look it up in the archives, this is my view on it: Shipping
> pre-compiled really isn't an option, as the size increase would be
> unacceptable - not only from a debian archive/bandwidth POV, but also
> from an older machine/tiddy HD POV.
Agreed.
> install python2.2 + friends on a 486 with 16 meg'o'ram :) Maybe it would
> be an idea to provide a script that the user can run when he feels the
> machine isn't needed for anything else.
This doesn't sound like a bad idea, but the compiled file for python
packages are currently put in /usr (not /usr/local), along with their
corresponding .py. The packages create them in postinst and therefore
take the responsibility of deleting them when the package is removed. If
we let the admin create the compiled files in /usr with a script (à la
compileall.py), he might be surprised to see them removed with the
corresponding package. This can be argued about, however.
> Anyway, I've done my uninformed butting in, and will return to lurk
> mode.
Well, noone asked you to do so (that is, to return to lurk), AFAIK. My
answer wasn't meant to sound offensive.
--
Florent
--
To UNSUBSCRIBE, email to debian-python-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: