[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bytecode compilation



On Thu, Jul 25, 2002 at 10:21:07PM +0200, Florent Rougon wrote:
> Dave Swegen <dswegen@software.plasmon.com> wrote:
> 
> > 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.

How about letting compileall.py inform the user at the end of the run
that compiled files will be deleted when the package is uninstalled?
That way the user has been given fair warning.

But yes, it isn't very pretty, and probably steps on the toe of some
policy or other.

> 
> > 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.

Apologies if it came across that I was offended. It is merely that I'm
too lazy to often de-lurk :)

Cheers
    Dave


-- 
To UNSUBSCRIBE, email to debian-python-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: