Update pyparsing requirement from ~=2.0 to >=2,<4#296
Merged
darthbear merged 1 commit intochimpler:masterfrom Feb 12, 2023
ecederstrand:patch-1
Merged
Update pyparsing requirement from ~=2.0 to >=2,<4#296darthbear merged 1 commit intochimpler:masterfrom ecederstrand:patch-1
darthbear merged 1 commit intochimpler:masterfrom
ecederstrand:patch-1
Conversation
Do so only for Python 3 since pyparsing 3 dropped support for Python 2 Replaces #276
Contributor
Author
|
Ping @darthbear ? |
Member
|
Thank yo @ecederstrand for your PR! |
darthbear
pushed a commit
that referenced
this pull request
Feb 12, 2023
Do so only for Python 3 since pyparsing 3 dropped support for Python 2 Replaces #276
|
so finally it is compatible with pyparsing 3.x? 🥳 |
This file contains hidden or 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
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.
Do so only for Python 3 since pyparsing 3 dropped support for Python 2
Replaces #276