Mark Dickinson added the comment: 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. ---------- nosy: +mark.dickinson resolution: -> rejected type: behavior -> enhancement _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22563> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
