-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
Meta ticket: fix docstring markups #34157
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:18
What should we do with
Normalize all to |
comment:19
Replying to @mkoeppe:
According to https://doc.sagemath.org/html/en/developer/coding_basics.html#sage-documentation-style
|
comment:20
Replying to @mkoeppe:
Probably both. People will write new code by imitating what they see in the old code, so the more we match the guidelines, the better. (This is another case like the blank lines between list items where I don't see the point in having a strict guideline. In this case we actually have one in place, so we should follow it.) |
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:24
To test with the bugfix release of the linter, regenerate the toxenv using |
comment:25
Remaining failures:
|
comment:46
this should be extended to pyx files too EDIT: see #34305 |
comment:47
Please rebase. |
comment:48
No need, it merges cleanly with 9.7.beta8 when done manually |
Changed branch from u/mkoeppe/meta_ticket__fix_docstring_markups to |
Originated from #30448.
We fix
https://github.com/sagemath/sagetrac-mirror/runs/7294638131?check_suite_focus=true
by chunks through
and a few commits that finish the job here on the ticket.
Depends on #30448
Depends on #34156
Depends on #34158
Depends on #34159
Depends on #34160
Depends on #34161
Depends on #34162
Depends on #34163
Depends on #34164
Depends on #34165
Depends on #34166
Depends on #34167
Depends on #34168
Depends on #34169
Depends on #34170
Depends on #34171
Depends on #34172
Depends on #34139
CC: @tscrim @fchapoton
Component: documentation
Author: Matthias Koeppe
Branch/Commit:
3b9399d
Reviewer: Kwankyu Lee
Issue created by migration from https://trac.sagemath.org/ticket/34157
The text was updated successfully, but these errors were encountered: