Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for #1792 #1794

Merged
merged 2 commits into from Feb 27, 2013
Merged

Fix for #1792 #1794

merged 2 commits into from Feb 27, 2013

Conversation

astrofrog
Copy link
Contributor

As of pyparsing 2.0.0, Python 2 is no longer supported, so we need to set an upper limit for the range of versions installable by pip.

… set an upper limit for the range of versions installable by pip
@@ -939,7 +939,7 @@ def get_install_requires(self):
if sys.version_info[0] >= 3:
return ['pyparsing>=2.0.0']
else:
return ['pyparsing>=1.5.6']
return ['pyparsing>=1.5.6,<=1.5.7']
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For future proofing should this not be 2.0.0?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, you mean strictly less than 2.0.0?

@astrofrog
Copy link
Contributor Author

@pelson - I fixed the version requirement to make it future proof, on the assumption that the 1.x branch of pyparsing will always remain Python 2 compatible.

@astrofrog
Copy link
Contributor Author

@pelson - it looks like Travis passed, so feel free to merge if you are happy with it.

@mdboom
Copy link
Member

mdboom commented Feb 27, 2013

Yeah -- I had thought pip would handle the Python version difference, but apparently not. I think this is the correct fix.

@mdboom
Copy link
Member

mdboom commented Feb 27, 2013

Also see the tangentially related #1788

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants