Jonathan Daugherty wrote > but these issues don't render the separation of scoped > functionality unimportant.
I think that this scoping is of *far* less importance than working vaguely like normal python modules and classes. Can anyone honestly say they expected to have to import things at method scope when making a custom instance or manipulator method? I think this seperation is a 'nice to have' feature. But I think than in the trade off, I would prefer it to suffer than 'acting like a normal class'. And there are lots and lots of ways to do it other than generating a whole new class in a whole new module, which shouldn't be rejected purely because they are slightly different than what we are currently used to. > Maybe the best thing to do would be to round up as many newcomers as > possible and see what they think would be clearer. > Not being funny, but this isn't actually a very good way to design anything. 'Most' newcomers will design a horrifically bad api if asked, because 'most' newcomers have no idea how to design apis.
