RetroSearch Browse

Mon Jul 27 03:05:55 CEST 2009 · http://mail.python.org/pipermail/python-dev/2009-July/090876.html

Joshua Haberman wrote:
> This is not as bad as having someone
> set __class__ on one of my instances, or set attributes on my type, etc.

Is there any real need to prevent someone from doing
those things?

Note that even when you are allowed to change the
__class__ of an instance, you're still prevented
from changing it to something that has a different
C layout, so you can't crash the intepreter that
way.

Similarly, built-in methods check that they're
given an object of appropriate type at the C
level.

My suggestion is to just let it be a full heap
type and accept whatever consequences follow.

-- 
Greg

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2009-July/090876.html below:

[Python-Dev] Py_TPFLAGS_HEAPTYPE too overloaded