[issue9875] Garbage output when running setup.py on Windows

2010-09-20 Thread Éric Araujo
Éric Araujo added the comment: This is indeed invalid. In distutils2, we’re removing the custom log module in favor of standard logging, and I’ve added a note on my todo list to check that verbosity option passed to setup scripts do impact module-level logging calls. -- resolution:

[issue9875] Garbage output when running setup.py on Windows

2010-09-16 Thread Jean-Paul Calderone
Jean-Paul Calderone added the comment: This seems to have been caused by an ill-placed distutils.log.set_verbosity(3) call. With that removed, this output isn't generated by default. So perhaps this is invalid, feel free to close it as so if you agree. -- __

[issue9875] Garbage output when running setup.py on Windows

2010-09-16 Thread Jean-Paul Calderone
New submission from Jean-Paul Calderone : The output of setup.py is polluted with this log message: Importing new compiler from distutils.msvc9compiler on Windows. For example, using pyOpenSSL's setup.py, running "setup.py --version" produces this output: Importing new compiler from dist