This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Unconditionally state when a build succeeds
Type: Stage: needs patch
Components: Versions: Python 3.6
process
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: brett.cannon Nosy List: brett.cannon
Priority: normal Keywords:

Created on 2016-08-26 17:56 by brett.cannon, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg273712 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2016-08-26 17:56
When setup.py succeeds at building but couldn't build some dependency it says "Python build finished successfully!" and then lists the modules that couldn't be built. But if you are able to actually build everything then nothing is printed to stdout. Due to the fact that getting everything to build takes so much effort, when I finally reached the nirvana that is all modules built I thought my build had actually failed thanks to nothing being printed to stdout.

It might be worth always printing out that the build succeeded no matter whether a extension module had issues being built or not.
msg274928 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2016-09-08 00:11
I'm not going to do this because I'm willing to bet someone is relying on the fact nothing is printed to stdout. Benjamin says that if you're not happy with this then "you're not a well-behaved UNIX user".
History
Date User Action Args
2022-04-11 14:58:35adminsetgithub: 72055
2016-09-08 00:11:39brett.cannonsetstatus: open -> closed
resolution: rejected
messages: + msg274928
2016-08-26 17:56:35brett.cannoncreate