Upgrade requirement to pyparsing 2.0.1 #2240
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
|
Shouldn't the install test al least drop the check for pyparsing < 2.0.0 in |
…atible with Python 2.x
|
@jenshnielsen: That's a good point. See attached. We should be able to squeak this into 1.3.0 final. However, I will put of solving the deprecation warnings, since we need to remain compatible with pyparsing < 2.0.0 |
|
Thanks. I have tested rc5 with pyparsing 2.0.1 on both python 27.5 and 3.3.2 and all tests pass. I agree that the solution to the deprecation warnings should wait until post 1.3.0 |
mdboom
added a commit
that referenced
this pull request
Jul 23, 2013
…ment Upgrade requirement to pyparsing 2.0.1
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.
The newly released pyparsing 2.0.1 fixes a number of problems with supporting Python 2.x and 3.x at the same time. Unfortunately, I think the ship has sailed to get this in for 1.3.0, but for 1.3.1 we should be able to do this.
http://code.activestate.com/lists/python-list/647675/