Martin Panter added the comment: I agree, SplitResult._replace() would probably have been very useful to me in the past if it were available (and guaranteed by the documentation).
The namedtuple implementation was added in revision 79579fa8d752 (in 2.6 and 3.0), with a comment mentioning speeding up and simplifying the code. So it may not have originally been intended to have the namedtuple functionality as part of the API. If the change is made in 3.5, it should equally be made in 2.7 (with a notice about only being supported since 2.6). ---------- nosy: +martin.panter, rhettinger _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27464> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
