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 Guido.van.Rossum, Mark.Shannon, benjamin.peterson, eltoder, larry, lemburg, njs, pitrou, rhettinger, serhiy.storchaka
Date 2015-09-01.08:30:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
Guido, do you have any thoughts on this?

Several of us (me included) think http://hg.python.org/lookup/c0d25de5919e probably should not have been done.  Mutating non-heap types crosses an implicit boundary that we've long resisted crossing because it opens a can worms and has potential to violate our expectations about how the language works.

[Mark Shannon]
> Breaking the interpreter in order to facilitate some obscure use case is unacceptable.

[Marc-Andre Lemburg]
I agree with Mark. This feature opens up a security hole large enough to drive a train through.

[Benjamin Peterson]
Probably the patch on that bug should be reverted.
  
[Larry Hastings]
As Python 3.5 Release Manager, my official statement is: Eek!
History
Date User Action Args
2015-09-01 08:30:45rhettingersetrecipients: + rhettinger, lemburg, pitrou, larry, benjamin.peterson, njs, Mark.Shannon, eltoder, serhiy.storchaka, Guido.van.Rossum
2015-09-01 08:30:45rhettingersetmessageid: <[email protected]>
2015-09-01 08:30:45rhettingerlinkissue24912 messages
2015-09-01 08:30:44rhettingercreate