Steven Bethard wrote: > Initially, I was concerned that this would break the symmetry with the > __metaclass__ signature:: > > def __metaclass__(name, bases, bodydict): > def __prepare__(name, bases, kwargs):
Can someone clarify something here: Are the keywords going to be passed to the prepare function only, or to both the the prepare function and the metaclass? If they're only passed to the prepare function, it means that any metaclass that's interested in them will have to implement a prepare function that creates some object to hold onto them, even if it has no other need for a custom namespace. If they're passed to both, then the signatures become metaclass.__prepare__(name, bases, **kwargs) metaclass(name, bases, body, **kwargs) BTW, I don't think I like the name "__prepare__" much more than "__metacreate__". It seems just as wooly. What's being prepared? How? What for? -- Greg _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
