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 martin.panter
Recipients jwilk, martin.panter, pitrou, serhiy.storchaka
Date 2015-03-22.13:29:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Well with a regular BufferedWriter, the chained exception is the same type as the original exception, so it does not really matter. I was just using the out-of-space exception as an easy way to get the body() method to abort in the middle of a command.

The problem with the NNTP library is that the NNTP class assumes that it can send a QUIT command when it shouldn’t be. The result can be a giant error message full of apparent garbage data, rather like in Issue 21468.

The minimum behaviour that I expect is that when the context manager exits, it should not cause a double exception with a different error type. My patch closes the connection as soon as an unrecoverable error happens, so __exit__() will not send a QUIT command and receive an invalid response.
Date User Action Args
2015-03-22 13:29:09martin.pantersetrecipients: + martin.panter, pitrou, jwilk, serhiy.storchaka
2015-03-22 13:29:09martin.pantersetmessageid: <>
2015-03-22 13:29:09martin.panterlinkissue22350 messages
2015-03-22 13:29:08martin.pantercreate