Ken Williams <kena...@gmail.com> added the comment:
This situation still seems to be the case in 2022. The output of `make
altinstall` has thousands of lines like
/usr/bin/install -c -m 644 ./Lib/test/__main__.py /usr/local/lib/python3.8/test
/usr/bin/install -c -m 644 ./Lib/test/_test_multiprocessing.py
/usr/local/lib/python3.8/test
/usr/bin/install -c -m 644 ./Lib/test/allsans.pem /usr/local/lib/python3.8/test
/usr/bin/install -c -m 644 ./Lib/test/ann_module.py
/usr/local/lib/python3.8/test
/usr/bin/install -c -m 644 ./Lib/test/ann_module2.py
/usr/local/lib/python3.8/test
/usr/bin/install -c -m 644 ./Lib/test/ann_module3.py
/usr/local/lib/python3.8/test
and
changing mode of
/usr/local/lib/python3.8/lib-dynload/_sysconfigdata__linux_x86_64-linux-gnu.py
to 644
changing mode of
/usr/local/lib/python3.8/lib-dynload/_sqlite3.cpython-38-x86_64-linux-gnu.so to
755
changing mode of
/usr/local/lib/python3.8/lib-dynload/array.cpython-38-x86_64-linux-gnu.so to 755
changing mode of
/usr/local/lib/python3.8/lib-dynload/_posixshmem.cpython-38-x86_64-linux-gnu.so
to 755
changing mode of
/usr/local/lib/python3.8/lib-dynload/_testmultiphase.cpython-38-x86_64-linux-gnu.so
to 755
changing mode of
/usr/local/lib/python3.8/lib-dynload/_codecs_cn.cpython-38-x86_64-linux-gnu.so
to 755
and
Compiling '/usr/local/lib/python3.7/test/test_file.py'...
Compiling '/usr/local/lib/python3.7/test/test_file_eintr.py'...
Compiling '/usr/local/lib/python3.7/test/test_filecmp.py'...
Compiling '/usr/local/lib/python3.7/test/test_fileinput.py'...
Compiling '/usr/local/lib/python3.7/test/test_fileio.py'...
Compiling '/usr/local/lib/python3.7/test/test_finalization.py'...
Compiling '/usr/local/lib/python3.7/test/test_float.py'...
Compiling '/usr/local/lib/python3.7/test/test_flufl.py'...
For me, the problem this causes is that CI build logs get extremely long, so
long that my CI build tools won't show the log in the browser anymore and it
makes it quite hard to figure out where problems are happening.
It looks like the problem is simply that there are lots of `echo` statements in
the Makefile.pre.in that could be conditioned on `--quiet`. One small example
(in the 'libinstall' target):
if test -x $$i; then \
echo $(INSTALL_SCRIPT) $$i $$b; \
$(INSTALL_SCRIPT) $$i $(DESTDIR)$$b; \
else \
echo $(INSTALL_DATA) $$i $$b; \
$(INSTALL_DATA) $$i $(DESTDIR)$$b; \
I don't quite understand how `--quiet` actually gets parsed and recognized by
the Makefile, though.
----------
nosy: +kenahoo
versions: +Python 3.10, Python 3.11, Python 3.7, Python 3.8, Python 3.9
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue29985>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
