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 r.david.murray
Recipients benjamin.peterson, docs@python, ezio.melotti, lemburg, martin.panter, pitrou, r.david.murray, rhettinger, serhiy.storchaka, swanson, vstinner
Date 2015-05-21.03:17:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432178261.77.0.839594080888.issue24243@psf.upfronthosting.co.za>
In-reply-to
Content
Raymond: this is currently marked as a documentation bug, and documentation is mostly what the OP was asking for.  So I'm reopening it.

That said, I think it is very appropriate to discuss fixing the behavior of string's endswith and startswith, because people are still (and will be for a while yet) porting from python2 and supporting single-code-base code, where string behaves the way bytes does in python3.  That should be addressed in a separate issue.  So in fact, history and "code written for the current behavior" comes down, IMO, on the side of fixing this edge case.  I'm willing to be argued out of that, though :)
History
Date User Action Args
2015-05-21 03:17:41r.david.murraysetrecipients: + r.david.murray, lemburg, rhettinger, pitrou, vstinner, benjamin.peterson, ezio.melotti, docs@python, martin.panter, serhiy.storchaka, swanson
2015-05-21 03:17:41r.david.murraysetmessageid: <1432178261.77.0.839594080888.issue24243@psf.upfronthosting.co.za>
2015-05-21 03:17:41r.david.murraylinkissue24243 messages
2015-05-21 03:17:41r.david.murraycreate