docs(ranges): add .. versionadded:: 26.3 to the public VersionRange class#1303
Merged
Merged
Conversation
notatallshaw
approved these changes
Jun 28, 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.
The public
VersionRangeclass (the wholesrc/packaging/ranges.pymodule, shipped in #1267 and extended in #1298) carries no version directive, while the method that produces it —SpecifierSet.to_range()— already declares.. versionadded:: 26.3(specifiers.py:1129). The other recently-added public classes carry a class-level directive as well:Versionhas.. versionadded:: 26.0andMarkerhas.. versionchanged:: 26.2.This adds
.. versionadded:: 26.3to theVersionRangeclass docstring, placed as the last docstring element to matchto_range/Version.docs/ranges.rstrenders it through.. automodule:: packaging.ranges, so readers of the reference learn which release first ships the API.Pure docs — no code change. No changelog entry, since the feature is already recorded under
:pull:1267``.