FIX: Change is comparison to == for tuple #1009
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
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.
Just here to try to help get to 5.0.0. I don't directly use rdflib, so I'm not familiar enough with the API to add a good test. Also, your coverage stats make it hard to see if this is getting properly exercised.
Assuming it is, my guess is that this is just a short-circuit to save some computation, and
(None, None, None)would generate the same result going the long way round. If so, then there's not much to test anyway.Long story short: Happy to add a test, if someone more familiar with the code base gives me a strong prod.
Closes #998.