This repository has been archived by the owner on May 11, 2021. It is now read-only.
Update gargoyle/conditions.py #22
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
adamchainz
force-pushed
the
merge_upstream_55
branch
3 times, most recently
from
33f1a45
to
3cac1e3
Compare
Merges disqus#55, thanks @matclayton. Added tests for `Range` by constructing a `ConditionSet` and testing the range on that - the test fails before this patch.
adamchainz
force-pushed
the
merge_upstream_55
branch
from
3cac1e3
to
5203879
Compare
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.
Fix Range condition
Merges disqus#55, thanks @matclayton .
Need:
Range, even indirectly, afaict.