Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parsing Epytext #35

Closed
biomadeira opened this issue Feb 27, 2015 · 5 comments

Comments

Projects
None yet
5 participants
@biomadeira
Copy link

commented Feb 27, 2015

Sorry the ignorance. Is there a way of 'forcing' pdoc to parse docstrings in Epytext format as the example below:

def load_config(filename, option):
    """
    Loads and tests input parameters.

    @param filename: input filename
    @param option: option name
    @return: returns a valid config value
    """

Thanks

@BurntSushi

This comment has been minimized.

Copy link
Contributor

commented Feb 27, 2015

No, but you could modify the templates to do whatever you want pretty easily: https://github.com/BurntSushi/pdoc/blob/master/pdoc/templates/html.mako#L66

@biomadeira

This comment has been minimized.

Copy link
Author

commented Feb 27, 2015

Nice. Thanks!

@johnyf

This comment has been minimized.

Copy link

commented Jun 16, 2015

I am also interested in this. Being an epydocuser myself, for some time now I have been using Epytext with markdown formatting. Though I am not aware of a suitable doc tool, I was planning to write one. The closest thing is to adapt pdoc for recognizing @param, @type, @return, @rtype, and also link automatically Name, replacing the Epytext [Name], if Name is found to be an existing class/function/etc somewhere in the package.

@peterjc

This comment has been minimized.

Copy link

commented Jul 29, 2016

I missed this issue when I filed #111 for the wider issue of supporting some of the markup languages as supported in epydoc (which does not support markdown).

@cortesi

This comment has been minimized.

Copy link
Member

commented Jun 3, 2018

Please see #153 for a unified discussion ticket about docstring flavors.

@cortesi cortesi closed this Jun 3, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.