The interface supported by that attribute will be fairly variable. Although 
there is some overlap between the RSA and DSA APIs so far I believe that's 
mostly happy coincidence. Users will probably need to use isinstance to 
figure out what to do in some cases. Once we support DSA it will be easier 
to write a good example of that.


On 31 March 2014 21:34:26 Glyph <notifications@github.com> wrote:

> > +                            structure could not be decoded successfully.
> > +
> > +        :raises TypeError: If a ``password`` was given and the private 
> key was
> > +                           not encrypted. Or if the key was encrypted but no
> > +                           password was supplied.
> > +
> > +        :raises UnsupportedAlgorithm: If the serialized key is of a type 
> that
> > +                                      is not supported by the backend.
> > +
> > +        :raises UnsupportedCipher: If the serialized key is encrypted with a
> > +                                   cipher that is not supported by the 
> backend.
> > +
> > +    .. attribute:: private_key
> > +
> > +        The deserialized private key object. An instance of any of the 
> private
> > +        key types supported by ``cryptography``.
>
> More specifically: what is the interface supported by this attribute? What 
> methods might I expect it to have?
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/pyca/cryptography/pull/627/files#r11135349