Message 149464 - Python tracker

➜

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	gjb1002
Recipients	docs@python, gjb1002
Date	2011-12-14.18:38:00
SpamBayes Score	0.002823095
Marked as misclassified	No
Message-id	<1323887881.83.0.596639258787.issue13597@psf.upfronthosting.co.za>
In-reply-to

Content
I would certainly be in favour of restoring the python 2.x behaviour, at least where standard error is concerned. When writing Python programs, it's important to see exceptions immediately, and not lose them entirely in some circumstances. I reported this as a documentation bug because I got the impression it was deliberate, mostly from reading http://bugs.python.org/issue4705 and the comp.lang.python thread in the description, but I personally think the Python 2.x behaviour was preferable.

I would certainly be in favour of restoring the python 2.x behaviour, at least where standard error is concerned. When writing Python programs, it's important to see exceptions immediately, and not lose them entirely in some circumstances.

I reported this as a documentation bug because I got the impression it was deliberate, mostly from reading http://bugs.python.org/issue4705 and the comp.lang.python thread in the description, but I personally think the Python 2.x behaviour was preferable.

History
Date	User	Action	Args
2011-12-14 18:38:01	gjb1002	set	recipients: + gjb1002, docs@python
2011-12-14 18:38:01	gjb1002	set	messageid: <1323887881.83.0.596639258787.issue13597@psf.upfronthosting.co.za>
2011-12-14 18:38:01	gjb1002	link	issue13597 messages
2011-12-14 18:38:00	gjb1002	create