[issue13346] re.split() should behave like string.split() for maxsplit=0 and maxsplit=-1

Ezio Melotti report at bugs.python.org
Sat Nov 5 04:03:22 CET 2011


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

This is a known issue, but I don't think it can be fixed without breaking backward compatibility.  The behavior with negative values is not explicitly documented, so I would consider it an implementation detail. The behavior with positive values is documented for both the functions.  Also even if it's inconsistent, I would expect people to request at least 1 split, otherwise they are basically asking for a no-op.
I suggest to close this as wontfix

----------
nosy: +ezio.melotti, rhettinger
resolution:  -> wont fix
versions: +Python 2.7, Python 3.2, Python 3.3 -Python 2.6

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


More information about the Python-bugs-list mailing list