[Twisted-Python] New components questions

Itamar Shtull-Trauring itamar at itamarst.org
Fri May 7 22:59:35 EDT 2004

On Fri, 2004-05-07 at 22:44, Glyph Lefkowitz wrote:

> Yeah. agreed.  Just make sure that the _adapter_ can still say that it
> doesn't want to be persistent; code that really, really seriously wants
> to remove a persistent adapter after it's created one can do just that;
> componentized.unsetComponent.

That's internal code in Adapter and Componentized, no? I won't be
touching that.

> Is it possible that we can move to a new-style Componentized somewhere
> else?  There are a lot of slightly-incompatible changes I'd like to
> make, most especially to slotlessly subclass dict, so that the unweildy
> names like 'setComponent' and 'unsetComponent' become 'x[IY] = y' and
> 'del x[IY]', and to save space on what should be as lightweight an
> object as possible...

Sure, think up a new name. To be honest, I think the way Componentized
interacts with Adapter is ugly. I haven't looked at it closely enough to
be sure exactly why - I just glanced at it, but really I'd think a
special method that returns some info to the Componentized would be
cleaner than checking attributes. Or something.

Itamar Shtull-Trauring    http://itamarst.org
Looking for a job -- http://itamarst.org/resume.html

More information about the Twisted-Python mailing list