[DOC] np.kron use double backticks for non-references #17993
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some part of the docstring were between simple backticks which are therefore marked as cross-reference, while I belive the intended role is likely verbatim.
|
These types of PRs are fine. They should be reflected in a decrease in the number of warnings in the build devdocs /wref warnings CI run, which prints out near the end |
|
Thanks @Carreau |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some part of the docstring were between simple backticks which are
therefore marked as cross-reference, while I beleive the intended role is
likely verbatim.
And apologies for the few PRs I'm working on a side project about documentation and use numpy as a guinea pig; if you find those PRs annoying or that I'm nitpicking too much; I'm happy to just left those be...