-
-
Notifications
You must be signed in to change notification settings - Fork 297
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
Display Text{String}
from python docstring as plain string instead of markdown
#1727
Comments
Text{Plain}
as plain string instead of markdownText{String}
from python docstring as plain string instead of markdown
I'd say this is an issue in PyCall. |
If we're returning a Shouldn't you be checking |
Even from Julia, documentation can be any show-able object, and you're supposed to be using the multimedia I/O machinery to decide how to |
@stevengj its an exception so PyCall docs work |
I'm confused, why do you need an "exception" rather than just using |
Because PyCall (or python itself, don't know how deep this is embedded) doesn't think about exposing it as markdown (instead using Ideally this would be fixed at a deeper layer, but AFAIK this fix works enough. What problem are you addressing? |
You can't assume this. There are lots of Python packages with non-markdown docstrings If an object doesn't have a |
Thanks for your feedback |
In #1239, I complained about python documentation not displayed in Pluto notebooks, which has been partially fixed in 0757a34 by parsing the returned docstring as markdown.
However, in my observation, python docstring is not standard markdown, at least not conformant to Julia's specification. For example, double backticks "``" are interpreted by Julia as LaTeX, but by Python (Sphinx) as inline code.
As a result, documentation for
sympy.fourier_transform
from SymPy.jl andplot
from PyPlot.jl are not rendered perfectly:The text was updated successfully, but these errors were encountered: