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 rhettinger
Recipients Isaac Morland, ethan.furman, methane, r.david.murray, rhettinger, steven.daprano
Date 2017-08-03.02:11:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1501726270.06.0.330454101673.issue31085@psf.upfronthosting.co.za>
In-reply-to
Content
> Also it's far from clear that the pre-renaming field names are 
> what is wanted in the auto-generated typename.

I concur.


> Anyway I think I'm probably out at this point.

Okay, marking this as closed.  Thank you for the suggestion.  Sorry this didn't pan out.


> I think Python development is not a good cultural fit
> for me, based on this discussion. 

This particular proposal didn't seem compelling to us.  Other suggestions are welcome.  If you're the same Isaac Morlund who participated in the initial development of namedtuple() ten years ago, then you should know that the design of the _replace() method was principally due to your suggestion.
History
Date User Action Args
2017-08-03 02:11:10rhettingersetrecipients: + rhettinger, steven.daprano, r.david.murray, methane, ethan.furman, Isaac Morland
2017-08-03 02:11:10rhettingersetmessageid: <1501726270.06.0.330454101673.issue31085@psf.upfronthosting.co.za>
2017-08-03 02:11:10rhettingerlinkissue31085 messages
2017-08-03 02:11:09rhettingercreate