Message 270150 - Python tracker

➜

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	martin.panter
Recipients	docs@python, kmike, martin.panter, rhettinger
Date	2016-07-11.01:30:46
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1468200647.36.0.583853727452.issue27464@psf.upfronthosting.co.za>
In-reply-to

Content
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).

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

History
Date	User	Action	Args
2016-07-11 01:30:47	martin.panter	set	recipients: + martin.panter, rhettinger, docs@python, kmike
2016-07-11 01:30:47	martin.panter	set	messageid: <1468200647.36.0.583853727452.issue27464@psf.upfronthosting.co.za>
2016-07-11 01:30:47	martin.panter	link	issue27464 messages
2016-07-11 01:30:46	martin.panter	create