Logged In: YES 
user_id=8861

Sorry, I don't agree entirely with either of the responses.

1) I should have said no commonly used *on-screen* entity
has this behavior. Backward compatibility can be handled
easily by creating new subclasses of Image that have the
proposed behavior. (I think I also disagree with the
behavior for Variables, since unsetting a variable can also
cause the screen appearance to change, but I haven't thought
about it carefully enough to have a strong opinion.)

2) This is true only if the last reference to the image is
the one being held by CPython. If a circular structure
refers to an image, the last reference will be deleted by
the garbage collector, not by CPython, so the image will not
disappear until garbage collection occurs.

I understand the reasoning, and it's not worth it to me to
go through the PEP process; I just don't agree.