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 chalmerlowe
Recipients BreamoreBoy, JoelLuellwitz, Lynne.Qu, benjamin.peterson, brian.curtin, chalmerlowe, terry.reedy
Date 2015-04-13.20:29:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1428956949.5.0.112384979489.issue11754@psf.upfronthosting.co.za>
In-reply-to
Content
Discussed with David Murray at PyCon Sprints 2015.
Considered the fact that to preserve backwards compatibility, it seems important that rather than
a) merely checking for the presence of each constant string (as the test does now) OR
b) checking for each desired character (regardless of order) as noted in msg221766

the tests should check for the exact strings that have historically been published in Python. Doing so seems to be the right path to ensure that:
a) the strings exist AND
b) the strings have not inadvertently changed.
History
Date User Action Args
2015-04-13 20:29:09chalmerlowesetrecipients: + chalmerlowe, terry.reedy, benjamin.peterson, brian.curtin, BreamoreBoy, JoelLuellwitz, Lynne.Qu
2015-04-13 20:29:09chalmerlowesetmessageid: <1428956949.5.0.112384979489.issue11754@psf.upfronthosting.co.za>
2015-04-13 20:29:09chalmerlowelinkissue11754 messages
2015-04-13 20:29:09chalmerlowecreate