> ... currently the height and width properties of an Image object are
> removable from the ZMI. If you do that though, you can't add them
> back. Its sorta silly.
Well, after fiddling with it a for a while I've decided I never want
to open Image.py ever again, that code is just too far gone. I
> An additional declaration might help, something like
> "_addableProperties". Names specified in this sequence could be
> allowed as property names unless the instance (itself) already has
> an attribute of this name. Of course, something like this needs to
> be implemented and is currently not a
Jamie Heilman writes:
> ...
> I'm wondering if there's any reason why simply adding the properties
> and instance variables to the instance within __init__ would be a bad
> thing for properties that you want to declare removable.
The restriction is a precaution against an accidental overriding
There's this somewhat annoying issues surrounding objects that declare
removable properties in their classes, in that if you remove them, you
can't add them again because many times a class variable of the same
name already exists. (atleast thats my understanding of it, I suppose
I could be smokin
