libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomaz Muraus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-531) documentation output contains raw epytext
Date Mon, 17 Mar 2014 09:06:44 GMT

    [ https://issues.apache.org/jira/browse/LIBCLOUD-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937576#comment-13937576
] 

Tomaz Muraus commented on LIBCLOUD-531:
---------------------------------------

Hm, I have no idea how this happened. Quite a while ago I've added a check to prevent this
from happening - https://github.com/apache/libcloud/blob/trunk/setup.py#L181

In any case, thanks for the report. I will re-generate the docs for 0.13.2 and this is not
an issue anymore for newer versions, because we have moved to Sphinx style docstrings.

> documentation output contains raw epytext
> -----------------------------------------
>
>                 Key: LIBCLOUD-531
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-531
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.13.2
>            Reporter: Glyph Lefkowitz
>              Labels: docstrings
>
> As you can see on http://libcloud.apache.org/apidocs/0.13.2/libcloud.dns.base.Record.html,
the documentation contains raw epytext.  This can happen if you generate documentation without
the epydoc package installed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message