[docs] [issue24243] behavior for finding an empty string is inconsistent with documentation

R. David Murray report at bugs.python.org
Thu May 21 05:17:41 CEST 2015


R. David Murray added the comment:

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 :)

----------
resolution: not a bug -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue24243>
_______________________________________


More information about the docs mailing list