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 r.david.murray
Recipients eric.araujo, ezio.melotti, mastahyeti, mhcptg, orsenthil, r.david.murray
Date 2014-11-05.22:18:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1415225927.47.0.945700354046.issue15824@psf.upfronthosting.co.za>
In-reply-to
Content
Think of it as immutable like a string is immutable.  The cases are exactly parallel (the string function is of course named 'replace' since it doesn't have to deal with the 'arbitrary attribute names' problem namedtuple does), except that it is much easier to address the parts of a url using the namedtuple.

_replace is not a "weird secrete method", it is part of the public API of namedtuple.  I agree that using '_' is unfortunate.  I would have preferred a name pattern like _replace_, to make it clearer that it is *not* a private method.
History
Date User Action Args
2014-11-05 22:18:47r.david.murraysetrecipients: + r.david.murray, orsenthil, ezio.melotti, eric.araujo, mastahyeti, mhcptg
2014-11-05 22:18:47r.david.murraysetmessageid: <1415225927.47.0.945700354046.issue15824@psf.upfronthosting.co.za>
2014-11-05 22:18:47r.david.murraylinkissue15824 messages
2014-11-05 22:18:47r.david.murraycreate