Serhiy Storchaka added the comment:

I agree with Nathaniel, that this bug is not so critical to be release blocker. 
While it definitely should be fixed, it may wait for 3.5.1. Bug reproducing is 
not data driven, it needs executing special Python code, and when arbitrary 
Python code execution is available, there are a lot of other way to crash or 
compromise the interpreter. But I'm not sure that allowing __class__ assignment 
for larger domain of types is desirable. If we will desire that it is not, any 
enhancements to __class__ assignment should be withdrawn. May be __class__ 
assignment should be discouraged, deprecated and then disabled for all classes 
(in 3.6+), and other ways should be proposed to solve problems that are solved 
with __class__ assignment.

Nathaniel, can you provide a patch, that keeps the fix of a buffer overflow, 
but withdraws the ability to assign __class__ in cases that were disabled 
before?

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue24912>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to