-
-
Notifications
You must be signed in to change notification settings - Fork 197
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
Support Epytext docstring syntax (@param
)
#275
Comments
Is there a name for that format? Is that Epytext? If this is remotely standardized and not completely homegrown I'd be happy to merge a PR that adds support for it. :) If you (or anyone else) wants to contribute this, I'm happy to rig it up with the rest of pdoc. |
The |
:param
or @param
syntax@param
)
Quick update: pdoc now supports |
So |
|
Oh lol, it's supposed to be |
Apologies for interrupting the thread, but this doesn't seem to work. Test codedef random_ascii(length: int = 32) -> str: # {{{
"""
Return a random string of ASCII letters and digits.
:param length: Length of the random string.
:return: Random ASCII string.
"""
return "".join(choices(ascii_letters + digits, k=length)) # }}} Rendered documentation
|
Problem Description
As noted in #143 , many Python projects use the format
:param <param-name>: <description>
or@param <param-name>: <description>
, but this format for documenting function parameters is not recognized by pdoc.Proposal
I would love to see pdoc add support for these formats for documenting function parameters. I work with several projects that use this format. Additionally, I feel like this format looks better in the code (particularly inside of IDE help texts).
Alternatives
Converting these docstrings to the google or numpydoc formats described in #153 is burdensome for larger projects that want to switch to using pdoc, especially since pdoc otherwise works so beautifully out of the box.
Additional context
n/a
The text was updated successfully, but these errors were encountered: