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 docs@python, gone, r.david.murray, rhettinger, steven.daprano, veky
Date 2017-08-26.19:33:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1503776031.47.0.700489139049.issue31283@psf.upfronthosting.co.za>
In-reply-to
Content
I agree with the other commenters and recommend this be closed.  There doesn't seem to be a a useful issue here.  It seems more like a pedantic twisting of words that ignores how Python works (i.e. that you can specify a specific class to inherit from and that it is possible to either shadow or alter builtins).  I don't see any magic here beyond changing a variable name to refer to a new object while previous references (or builtin references) to that name continue to refer to old object.
History
Date User Action Args
2017-08-26 19:33:51rhettingersetrecipients: + rhettinger, steven.daprano, r.david.murray, docs@python, veky, gone
2017-08-26 19:33:51rhettingersetmessageid: <1503776031.47.0.700489139049.issue31283@psf.upfronthosting.co.za>
2017-08-26 19:33:51rhettingerlinkissue31283 messages
2017-08-26 19:33:51rhettingercreate