Fix # noqa rendering in docs #645
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
Move # noqa from inside docstrings to the end of the docstring to avoid rendering the # noqa tag in the documentation as reported in PyCQA#644.
lukehinds
approved these changes
Nov 19, 2020
1 task
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.
Move
# noqafrom inside docstrings to the end of the docstring. This avoids rendering the # noqa tag in the documentation as reported in #644 while preventing flagging the excessive line lengths in the linting.Note: I also added the
E501label to maintain the original intent of applying the# noqatag to the long lines only.Fixes #644.