You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should add the specific errors that a method can throw to the documentation (since the RFC documents this). If supplementary errors can be thrown, just use document the SupplementaryError class.
low-level API documented
high-level API documented
The text was updated successfully, but these errors were encountered:
Now that we have specific errors (found in `gssapi.raw.exceptions`),
we should document which errors can be thrown.
This commit does so for the low-level API. In the case where no
errors were documented, the only error documented was the generic
GSSError, otherwise, GSSError was removed, and the specific listed
errors were added (except in the case where GSS_S_FAILURE is
specifically listed, in which case so is GSSError).
Note that non-RFC extensions did not have specific errors documented,
since they do not have a standardized list of specific errors.
Part of #11
Now that we have specific errors (found in `gssapi.raw.exceptions`),
we should document which errors can be thrown.
This commit does so for the high-level API.
Closes#11
Now that we have specific errors (found in `gssapi.raw.exceptions`),
we should document which errors can be thrown.
This commit does so for the low-level API. In the case where no
errors were documented, the only error documented was the generic
GSSError, otherwise, GSSError was removed, and the specific listed
errors were added (except in the case where GSS_S_FAILURE is
specifically listed, in which case so is GSSError).
Note that non-RFC extensions did not have specific errors documented,
since they do not have a standardized list of specific errors.
Part of #11
We should add the specific errors that a method can throw to the documentation (since the RFC documents this). If supplementary errors can be thrown, just use document the
SupplementaryError
class.The text was updated successfully, but these errors were encountered: