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 comparison #132

Merged
merged 1 commit into from
May 29, 2019
Merged

Fix comparison #132

merged 1 commit into from
May 29, 2019

Conversation

Flamefire
Copy link
Contributor

@Flamefire Flamefire commented May 29, 2019

Continuation of stale #104 with fix for Python2

@scls19fr
Copy link
Member

@Flamefire could you rebase?

It should
Closes #102
Closes #103

@Flamefire Flamefire force-pushed the fix_comparison branch 3 times, most recently from a4d091f to 825b1bf Compare May 29, 2019 15:04
@Flamefire
Copy link
Contributor Author

This should work now. I extended the test case to include all operators in a <op> b and b <op> a.

Note that TypeError must be raised for unsupported comparisons. Otherwise Python assumes "Unimplemented" as in "wanted but not yet done" and does instance comparison as fall back and this is NOT wanted

@Flamefire
Copy link
Contributor Author

Ok, passing now. I cleaned the commits and squashed them into 1.

Can you push out a PyPi release too?

@scls19fr scls19fr merged commit 21f87f6 into python-semver:master May 29, 2019
@Flamefire Flamefire deleted the fix_comparison branch May 29, 2019 15:29
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

2 participants