Message 299554 - 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	methane
Recipients	Isaac Morland, ethan.furman, methane, rhettinger, steven.daprano
Date	2017-07-31.12:53:04
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1501505584.79.0.37655752839.issue31085@psf.upfronthosting.co.za>
In-reply-to

Content
When subclassing, current __repr__ uses `self.__class__.__name__`. So you get meaningful name already. When automatic generation, I recommend you to use some wrapper to cache same namedtuple, since creating namedtuple on the fly is costly job. I'm afraid "unnnamed" namedtuple may lead people to use namedtuple on the fly, like lambda.

When subclassing, current __repr__ uses `self.__class__.__name__`.  So you get meaningful name already.

When automatic generation, I recommend you to use some wrapper to cache same namedtuple, since creating namedtuple on the fly is costly job.

I'm afraid "unnnamed" namedtuple may lead people to use namedtuple on the fly, like lambda.

History
Date	User	Action	Args
2017-07-31 12:53:04	methane	set	recipients: + methane, rhettinger, steven.daprano, ethan.furman, Isaac Morland
2017-07-31 12:53:04	methane	set	messageid: <1501505584.79.0.37655752839.issue31085@psf.upfronthosting.co.za>
2017-07-31 12:53:04	methane	link	issue31085 messages
2017-07-31 12:53:04	methane	create