Regardless, getting back to the main goal I had when writing PEP 246 -- your alternative proposal still doesn't seem to provide a mechanism for component developers to have a dialogue with one another to connect components without involving the application programmer.
Eh? You still have adapt(); you still have adapters. The only difference is that I've specified a way to not need "interfaces" - instead interfaces can be defined in terms of individual operations, and those operations can be initially defined by an abstract base, concrete class, or an "interface" object. Oh, and you don't have to write adapter *classes* - you write adapting *methods* for individual operations. This can be done by the original author of a class or by a third party -- just like with PEP 246.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com