This discussion should move to the types-sig, types-sig@[...].org,
http://www.python.org/sigs/types-sig/.  I am cross posting to the
types sig.  Replies to this message should be posted to
types-sig@[...].org and *not* to comp.lang.python.

Paul Prescod wrote:
>  
>  This is almost identical to what we decided to implement at the
>  conference. The only catch is that __class_protocols__ is called
>  __interfaces__ and it is a list of interface objects. An interface object
>  looks a lot like a class (because we are using existing Python syntax
>  features) but it is conceptually a class with no implementation.

Actually, in my mind (and current implementation) it's actual and
conceptual connection to a class is pretty tenuous.  Asside from being 
created with a class statement, it doesn't look much like a class.
Interfaces are not classes and can't be subclassed with classes.
 
Jim

--
Jim Fulton           mailto:jim@[...].com
Technical Director   (888) 344-4332              Python Powered!
Digital Creations    http://www.digicool.com     http://www.python.org

Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
address may not be added to any commercial mail list with out my
permission.  Violation of my privacy with advertising or SPAM will
result in a suit for a MINIMUM of $500 damages/incident, $1500 for
repeats.