That was exactly my point. I've looked at a lot of frameworks over the years, but now if I see anything which imposes arbitrary behaviour, then I just hit the back button, and I think people get put off by seemingly arbitrary restrictions encoded in special ways. I'm trying not to be too controversial here, but if you look at various object publishing mechanisms, you see two things: that the developers assume that a rigid hierarchy is how everyone wants to design their applications; the various ways of telling the framework about exposed objects. Clearly, due to Python's introspection capabilities and the potential for security breaches (ask anyone who has written an object publisher about that) you need the special notation and it needn't be too intrusive (although Quixote's notation seems a bit contrived), but I can't help feeling that many people are thinking, "Hold on! I'm not sure if this even suits me."