[issue3722] print followed by exception eats print with doctest

Change by Chris Withers : -- keywords: -easy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue3722] print followed by exception eats print with doctest

Chris Withers added the comment: @iritkatriel - if Tim thinks this is hard, it probably is hard ;-) -- ___ Python tracker ___ ___

[issue3722] print followed by exception eats print with doctest

Change by Irit Katriel : -- keywords: +easy -patch versions: +Python 3.10 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list

[issue3722] print followed by exception eats print with doctest

Chris Withers ch...@simplistix.co.uk added the comment: Terry, My original post was not about *temporary* output inserted for debugging, but test mocks and the like which form a permanent part of the test and which output to stdout. cheers, Chris --

[issue3722] print followed by exception eats print with doctest

Terry J. Reedy tjre...@udel.edu added the comment: You misunderstood my last response. The first paragraph *dismisses* the case of temporary print (raised by Charles-Axle) as out of scope for doctests and hence this issue. The next ones addresses *your* case of code *permanently* intended to

[issue3722] print followed by exception eats print with doctest

Terry J. Reedy tjre...@udel.edu added the comment: Temporary output will break all doctests, not just those with exception traceback. One should fix, disable debug output, and then rerun doctest to make sure fix did not break anything else. A function that prints and raises *can* be tested as

[issue3722] print followed by exception eats print with doctest

Terry J. Reedy tjre...@udel.edu added the comment: For the purpose of this tracker, a 'bug' (behavior issue) is a discrepancy between doc and behavior. Micro ('bugfix') releases fix such discrepancies, which are all unintentional. Every feature request addresses what someone considers a

[issue3722] print followed by exception eats print with doctest

Georg Brandl ge...@python.org added the comment: It's not really my call. Tim is the author of the module and classified it as a feature request. Why don't you try to come up with a patch? He might even accept it :D -- nosy: +georg.brandl ___

[issue3722] print followed by exception eats print with doctest

Changes by Georg Brandl ge...@python.org: -- priority: - low type: behavior - feature request ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3722 ___

[issue3722] print followed by exception eats print with doctest

Chris Withers ch...@simplistix.co.uk added the comment: Hey Georg, I agree with the priority, but I'm still not convinced this is just a feature request. The piece of documentation that Tim is referring to is a tiny footnote in the doctest docs, and, as I said previously, I'm not sure

[issue3722] print followed by exception eats print with doctest

Charles-Axel Dein [EMAIL PROTECTED] added the comment: This is a bug. This is not a good behavior. If I would like to temporarily print a variable to see its content, in order to debug my code, doctest will eat its output. Thus I will be make to use pdb or to use logging, or to get rid of

[issue3722] print followed by exception eats print with doctest

Chris Withers [EMAIL PROTECTED] added the comment: Out of interest, where are the doctest docs you quoted? I missed that bit and that disturbs me :-S I'm not sure documenting a bug and trying to explain it away makes it any less of a bug, nonetheless, lets leave this one open as a feature

[issue3722] print followed by exception eats print with doctest

New submission from Chris Withers [EMAIL PROTECTED]: Here's an example from a python interpreter session: Python 2.4.4 (#71, Oct 18 2006, 08:34:43) [MSC v.1310 32 bit (Intel)] on win32 Type help, copyright, credits or license for more information. def test(): ... print hello ... raise

[issue3722] print followed by exception eats print with doctest

Chris Withers [EMAIL PROTECTED] added the comment: Here's the full test file. Added file: http://bugs.python.org/file11301/doctestbug.py ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3722 ___

[issue3722] print followed by exception eats print with doctest

Tim Peters [EMAIL PROTECTED] added the comment: As the doctest docs say, Examples containing both expected output and an exception are not supported. Trying to guess where one ends and the other begins is too error-prone, and that also makes for a confusing test. Since this is