[
https://issues.apache.org/jira/browse/LIBCLOUD-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150670#comment-14150670
]
Tomaz Muraus commented on LIBCLOUD-620:
---------------------------------------
Actually, ignore my last comment, I don't know what I was thinking.
We can't use that anymore since we have migrated to sphinx style docstring
format (previously we've used epytext) which is not supported by pydoctor which
we have used to generate API documentation in the past.
I will look into including complete API documentation in the new Sphinx
documentation (IIRC, this should be possible without a lot of effort).
> Exception Class Hierarchy Lost with Move to Readthedocs
> -------------------------------------------------------
>
> Key: LIBCLOUD-620
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-620
> Project: Libcloud
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 0.14.0-beta3
> Reporter: Will Bond
> Priority: Minor
>
> I am starting to work with libcloud and trying to write my code in a robust
> way to handle connection issues. Unfortunately there doesn't seem to be any
> documentation about exceptions, especially at the connection layer.
> It seems there used to be with old versions. For example:
> http://libcloud.apache.org/apidocs/0.13.2/classIndex.html. From what I can
> tell, starting with version 0.14.0 and the move to readthedocs, there is is
> no longer a way to get this info without reading the whole codebase.
> It would be really useful to provide something like this moving forward.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
