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.

Author techtonik
Recipients BreamoreBoy, alanjds, amaury.forgeotdarc, amiseler, jcea, mhammond, pysquared, santoso.wijaya, techtonik, tim.peters, tim_evans
Date 2013-06-26.10:34:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372242896.97.0.570961130475.issue706263@psf.upfronthosting.co.za>
In-reply-to
Content
This is still an issue for Python 2 users. Most important that pythonw.exe has a magic ability to fail silently leaving users with no means to create valid bug reports (the reason why StackOverflow questions are downvoted and erased).

http://bugs.ascend4.org/print_bug_page.php?bug_id=471
stream https://code.google.com/p/spyderlib/issues/detail?id=1260

The argument in msg15198 is somewhat misleading. If pythonw.exe fails because of print statement or because other issue, there is no way to report that.

Anyway, this reminds me very much of mod_wsgi, with only problem that Python developers don't receive as much feedback as Graham to make the change: http://blog.dscpl.com.au/2009/04/wsgi-and-printing-to-standard-output.html
History
Date User Action Args
2013-06-26 10:34:57techtoniksetrecipients: + techtonik, tim.peters, mhammond, jcea, pysquared, amaury.forgeotdarc, amiseler, tim_evans, alanjds, santoso.wijaya, BreamoreBoy
2013-06-26 10:34:56techtoniksetmessageid: <1372242896.97.0.570961130475.issue706263@psf.upfronthosting.co.za>
2013-06-26 10:34:56techtoniklinkissue706263 messages
2013-06-26 10:34:56techtonikcreate