Remove invalid escape sequence from docstring #296
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
lukpueh
reviewed
Oct 30, 2020
lukpueh
approved these changes
Oct 30, 2020
generate_public_and_private() docstring contains an invalid escape
sequence which can lead to an annoying
DeprecationWarning: invalid escape sequence
Remove the whole string as it does not seem very useful.
jku
force-pushed
the
fix-invalid-escape-sequence-in-docstring
branch
from
a3339cc to
3c0fd2e
Compare
|
🙇 |
Merged
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.
generate_public_and_private() docstring contains an invalid escape sequence which can lead to an annoying
DeprecationWarning: invalid escape sequenceRemove the whole string as it does not seem very useful.
The related issue is #290: this fixes half of it. Updating the vendored ed25519 will fix the other instance.