Upgrade pyparsing from 2.2.0 to 2.2.1 #5796
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
hugovk
commented
Sep 18, 2018
hugovk
force-pushed
the
upgrade-pyparsing
branch
from
309ec71 to
d90532f
Compare
pradyunsg
added
the
project: vendored dependency
pradyunsg
approved these changes
Sep 29, 2018
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
added
the
auto-locked
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
From https://github.com/pyparsing/pyparsing/blob/pyparsing_2.2.1/pyparsing.py, released today.
https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.2.1 says the release contains:
The deprecation warning is reported in #5013 and was fixed upstream in pyparsing/pyparsing#16.