➜

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 Shoham Peller, demian.brecht, djc, jwilk, karlcow, martin.panter, mschu, orsenthil
Date 2017-03-12.21:56:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489355762.84.0.100822498262.issue8450@psf.upfronthosting.co.za>
In-reply-to
Content 
I don’t think so. It is best to avoid a new exception type (even a subclass) in a bug fix. That would break code which checks “type(exc) == BadStatusLine” or similar.

Specific exception messages are supposed to be implementation details, and the current message is already quirky due to the change from Issue 7427 (released in 2.7a4). That is why I thought it might be reasonable to just change the exception message in a bug fix.
History
Date User Action Args
2017-03-12 21:56:02martin.pantersetrecipients: + martin.panter, orsenthil, jwilk, djc, karlcow, mschu, demian.brecht, Shoham Peller
2017-03-12 21:56:02martin.pantersetmessageid: <1489355762.84.0.100822498262.issue8450@psf.upfronthosting.co.za>
2017-03-12 21:56:02martin.panterlinkissue8450 messages
2017-03-12 21:56:02martin.pantercreate