fix escaping backslash in comments #9057
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
alexrashed
added
the
semver: patch
alexrashed
force-pushed
the
fix-asf-updates
branch
from
fc56d8c
to
aa71d8c
Compare
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.
Motivation
The latest version of
botocorecontains a change in the spec (namely boto/botocore@29dbcb9) which contains a backslash in the documentation of an operation of SESv2.API code generated based on this botocore version fail the linting check, because the generated docstring contains the
`\`(which violates flake8's W605).Changes
This PR just adds the backslash to the list of characters which need to be escaped in the docstring to fix the linting errors.
Testing
The SESv2 API has been generated based on the change and it passes the linting.