docs(specifiers): add is_unsatisfiable() usage example#1166
Open
docs(specifiers): add is_unsatisfiable() usage example#1166
Conversation
henryiii
approved these changes
Apr 19, 2026
This file contains hidden or 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
2 participants
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.
Fixes #1165
PR #1119 added
SpecifierSet.is_unsatisfiable()but the usage examples indocs/specifiers.rstdon't demonstrate it. Users scanning the Usage section have no way to discover this method without reading the full API reference.Added a doctest example showing
is_unsatisfiable()on both an unsatisfiable set (>=2.0,<1.0→True) and a satisfiable one (>=1.0,<2.0→False), placed after the existingfilter()example.