OpenID Libraries should be stateless

[Wichert Akkerman]

Previously Kevin Turner wrote:
> We do make an effort to preserve API compatibility between releases.
> It's true that, the farther you get away from consumer.Consumer and in
> to the internals of the code, the more cavalier we are about that -- I
> think Python interfaces are particularly prone to public/private
> interface confusion -- but parts that people have told us they need to
> use can be treated as public.  If we break those, we'll make a note of
> it in the NEWS file.

If you're interested in making proper interfaces, which imho is a good
idea, take a look at zope.interface. That is a reasonably standard
method to define public interfaces. Zope2, Zope3, twisted and probably
others all use it with great success. 

Wichert.

-- 
Wichert Akkerman <wichert at wiggy.net>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.