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 eric.araujo
Recipients Arfrever, eric.araujo, georg.brandl, hynek, ncoghlan, pitrou, r.david.murray, terry.reedy
Date 2012-07-02.19:51:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1341258669.44.0.103141030132.issue15180@psf.upfronthosting.co.za>
In-reply-to
Content
> This strikes me as a bugfix that does not get backported because code might depend on
> the bug. If the policy for exception messages, such as it is, documented somewhere?

I don’t know if it’s written anywhere, but the rule I follow is that even though exact error messages are not specified by the Python language, they should not be changed in bugfix releases (I seem to remember bugs for argparse and tarfile where this was invoked).  The commit policy seems in flux these days however, with code cleanups going in stable versions (urllib and collections recently).
History
Date User Action Args
2012-07-02 19:51:09eric.araujosetrecipients: + eric.araujo, georg.brandl, terry.reedy, ncoghlan, pitrou, Arfrever, r.david.murray, hynek
2012-07-02 19:51:09eric.araujosetmessageid: <1341258669.44.0.103141030132.issue15180@psf.upfronthosting.co.za>
2012-07-02 19:51:03eric.araujolinkissue15180 messages
2012-07-02 19:51:03eric.araujocreate