Message228647
IMO, this is a horrible idea. I'd hate for creation of a `namedtuple` class to fail just because there happened to be an existing (perhaps in an as-yet uncollected garbage `namedtuple` class with the same name). That's the kind of spooky "action at a distance" that makes debugging unnecessarily difficult.
I also think this would be pretty much impossible to implement efficiently. :-)
I'm closing this report here: this behaviour is not a bug, and the suggested exception raising is (IMO) both undesirable and unworkable in practice. I'd suggest opening a thread on the Python mailing-list if you want to discuss the idea further; if that thread produces a focused, widely accepted proposal, feel free to re-open an issue here. |
|
Date |
User |
Action |
Args |
2014-10-06 08:39:31 | mark.dickinson | set | recipients:
+ mark.dickinson, fhaxbox66@googlemail.com |
2014-10-06 08:39:31 | mark.dickinson | set | messageid: <1412584771.06.0.680134438959.issue22563@psf.upfronthosting.co.za> |
2014-10-06 08:39:31 | mark.dickinson | link | issue22563 messages |
2014-10-06 08:39:30 | mark.dickinson | create | |
|