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

Jean-Paul Calderone report at bugs.python.org
Thu Sep 16 16:19:52 CEST 2010


New submission from Jean-Paul Calderone <invalid at example.invalid>:

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 distutils.msvc9compiler
  0.10

But the version number of pyOpenSSL is "0.10", not "Importing new compiler from distutils.msvc9compiler\n0.10".

The --quiet flag does not solve this problem, apparently because this log message is done at the top-level of msvccompiler.py, perhaps before --quiet is interpreted.

This interferes with my build automation which depends on "setup.py --version" producing the version number of the project in order to properly compute certain filenames.

----------
assignee: tarek
components: Distutils
messages: 116552
nosy: eric.araujo, exarkun, tarek
priority: normal
severity: normal
status: open
title: Garbage output when running setup.py on Windows
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9875>
_______________________________________


More information about the Python-bugs-list mailing list