[issue73] setup.py --name prints warning messages to stdout, rather than stderr

New submission from Sridhar Ratnakumar <sridharr@activestate.com>: Warning messages must be printed to stderr. This allows for a programattic way to find setup.py metadata.
pwd ../dap.plugins.sql-0.2.1
apy setup.py --name 2> /dev/null 'dap.plugins' is declared as a package namespace, but 'dap' is not: please correct this in setup.py dap.plugins.sql
echo $? 0
---------- messages: 295 nosy: srid priority: bug status: unread title: setup.py --name prints warning messages to stdout, rather than stderr _______________________________________________ Setuptools tracker <setuptools@bugs.python.org> <http://bugs.python.org/setuptools/issue73> _______________________________________________

On Fri, May 29, 2009 at 12:57 PM, Sridhar Ratnakumar<setuptools@bugs.python.org> wrote:
New submission from Sridhar Ratnakumar <sridharr@activestate.com>:
Warning messages must be printed to stderr. This allows for a programattic way to find setup.py metadata.
pwd ../dap.plugins.sql-0.2.1
apy setup.py --name 2> /dev/null 'dap.plugins' is declared as a package namespace, but 'dap' is not: please correct this in setup.py dap.plugins.sql
echo $? 0
---------- messages: 295 nosy: srid priority: bug status: unread title: setup.py --name prints warning messages to stdout, rather than stderr
It should be easy to filter / redirect critical, debug, error, and warning messages to sys.stderr if there's a common logger for setuptools... My 2 cents, -Garrett

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Garrett Cooper wrote:
On Fri, May 29, 2009 at 12:57 PM, Sridhar Ratnakumar<setuptools@bugs.python.org> wrote:
New submission from Sridhar Ratnakumar <sridharr@activestate.com>:
Warning messages must be printed to stderr. This allows for a programattic way to find setup.py metadata.
pwd ../dap.plugins.sql-0.2.1
apy setup.py --name 2> /dev/null 'dap.plugins' is declared as a package namespace, but 'dap' is not: please correct this in setup.py dap.plugins.sql
echo $? 0
messages: 295 nosy: srid priority: bug status: unread title: setup.py --name prints warning messages to stdout, rather than stderr
It should be easy to filter / redirect critical, debug, error, and warning messages to sys.stderr if there's a common logger for setuptools...
This use case isn't logging: the entire point of running the command 'setup.py --name' is to print that text. IMHO it belongs on stdout, rather than stnderr. Switching it will break extant / deployed scripts. Other information printed while executing some command could be logging, and therefore a potential candidate for the logging module (which itself has issues about spew to standard pipes). Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKIutT+gerLs4ltQ4RArVnAKCDBMfFCcbYnPsRA4SRtT+FlrBQVACdFZBi J0JrglifE0+Cv+iJmq+zCzc= =+ODo -----END PGP SIGNATURE-----
participants (3)
-
Garrett Cooper
-
Sridhar Ratnakumar
-
Tres Seaver