-
Notifications
You must be signed in to change notification settings - Fork 53
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
Update __init__.py #571
Update __init__.py #571
Conversation
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## master #571 +/- ##
=======================================
Coverage 92.47% 92.47%
=======================================
Files 47 47
Lines 8170 8170
Branches 1948 1948
=======================================
Hits 7555 7555
Misses 358 358
Partials 257 257 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
Hi @Codeberg-AsGithubAlternative-buhtz, Do you want to follow up on this PR ? |
Hi @tristanlatr I also have no way to test the doc output before creating a new or modifying this PR. I love pydoctor but I won't waste more time of my life setting up sphinx beside of it. So I don't see how to test how my modifications will look like in HTML output. I assume also that I am confused about the original doc text. Sorry for wasting your time with an ugly PR. |
Hi @Codeberg-AsGithubAlternative-buhtz, Thanks for your kind words regarding pydoctor. I believe there is a comprehension issue, indeed. This changes have nothing to do with sphinx, maybe you got confused because the pydoctor theme that looks like readthedocs? Your proposal is to replace some Ho and by the way, you should not have to setup sphinx and everything if you install Tell me if things are more clear now, |
I think I got it now. This is totaly wrong what I have done because I mixed Escaping with Inline-Code. I will rewrite it later. Not tonight. ;) Sorry, but I have to say that this example-docu doesn't make sense. E.g. the "URL" section. This code is only understandable when read as code. But when it is rendered in HTML it doesn't make sense anymore. I will update that, too. The user need to understand and learn without reading the original source file init.py |
Thanks for your input, note that there is also this docs about epytext: http://epydoc.sourceforge.net/manual-epytext.html which are fully applicable to pydoctor except the part about « Indexed Terms ». I agree that our demo packages should improved. And better explained that they contains example code as well as extra documentation regarding the docformat syntax. |
So no please take a look. Would be glad to merge this because I don't use epydoc style. ;) |
Fix #567
Please check carefully if this is correct.