[issue37175] make install: make compileall optional

2019-06-07 Thread Ned Deily


Ned Deily  added the comment:

In many installations, the user running Python would not have write access to 
the lib directory tree where the compiled byte files need to be created so we 
would not want to change the current default behavior.  On the other hand, I 
could see some times when testing where it would speed things up to skip 
compiling.

The issue of tons of output is really a more important issue; it would be 
useful to be able to suppress all those lines of compile output as they rarely 
provide any useful information, perhaps even suppressing by default.

--
nosy: +ned.deily
versions: +Python 3.9 -Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue37175] make install: make compileall optional

2019-06-06 Thread daniel hahler


New submission from daniel hahler :

I'd like to make running compileall optionally during installation, since it 
takes quite a while by itself (with lots of output), and gets a bit into the 
way when installing often (e.g. with git-bisect).

AFAIK it should not be required, because the files would be compiled on demand 
as usual.

I could imagine having an explicit target for this, or a make variable to 
control this, i.e. "make install COMPILEALL=0".

--
components: Installation
messages: 344812
nosy: blueyed
priority: normal
severity: normal
status: open
title: make install: make compileall optional
type: enhancement
versions: Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com