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 gvanrossum
Recipients Guido.van.Rossum, Mark.Shannon, benjamin.peterson, eltoder, gvanrossum, larry, lemburg, ncoghlan, njs, pitrou, python-dev, rhettinger, serhiy.storchaka, vstinner
Date 2015-09-05.22:40:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441492820.0.0.475732507616.issue24912@psf.upfronthosting.co.za>
In-reply-to
Content
Mark, please calm down. Modules are incredibly simple objects compared to classes -- and yet you can change the __class__ of a class. You can also directly modify the __dict__ of a module. You can shoot yourself in the foot phenomenally this way, but that's not the point. The point is not to violate *internal* constraints of the interpreter. Changing immutable objects was violating such a constraint. Changing a module's __class__ is not.
History
Date User Action Args
2015-09-05 22:40:20gvanrossumsetrecipients: + gvanrossum, lemburg, rhettinger, ncoghlan, pitrou, vstinner, larry, benjamin.peterson, njs, Mark.Shannon, python-dev, eltoder, serhiy.storchaka, Guido.van.Rossum
2015-09-05 22:40:20gvanrossumsetmessageid: <1441492820.0.0.475732507616.issue24912@psf.upfronthosting.co.za>
2015-09-05 22:40:19gvanrossumlinkissue24912 messages
2015-09-05 22:40:19gvanrossumcreate