packaging_guide.rst: explain forward and backward compat before the less common cases #47402
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
spackbot-app
bot
added
core
haampie
force-pushed
the
hs/docs/forward-backward-bounds
branch
2 times, most recently
from
583a7be to
924255f
Compare
haampie
force-pushed
the
hs/docs/forward-backward-bounds
branch
from
924255f to
6ff6859
Compare
alalazo
reviewed
Nov 4, 2024
alalazo
reviewed
Nov 4, 2024
|
Supersedes the old PR #35002. |
alalazo
approved these changes
Nov 4, 2024
This was referenced Nov 4, 2024
Merged
haampie
added a commit
that referenced
this pull request
Nov 5, 2024
…ess common cases (#47402) The idea is to go from most to least used: backward compat -> forward compat -> pinning on major or major.minor version -> pinning specific, concrete versions. Further, the following ```python # backward compatibility with Python depends_on("[email protected]:") depends_on("[email protected]:", when="@1.2:") depends_on("[email protected]:", when="@1.4:") # forward compatibility with Python depends_on("python@:3.12", when="@:1.10") depends_on("python@:3.13", when="@:1.12") depends_on("python@:3.14") ``` is better than disjoint when ranges causing repetition of the rules on dependencies, and requiring frequent editing of existing lines after new releases are done: ```python depends_on("[email protected]:3.12", when="@:1.1") depends_on("[email protected]:3.12", when="@1.2:1.3") depends_on("[email protected]:3.12", when="@1.4:1.10") depends_on("[email protected]:3.13", when="@1.11:1.12") depends_on("[email protected]:3.14", when="@1.13:")
haampie
added a commit
that referenced
this pull request
Nov 18, 2024
…ess common cases (#47402) The idea is to go from most to least used: backward compat -> forward compat -> pinning on major or major.minor version -> pinning specific, concrete versions. Further, the following ```python # backward compatibility with Python depends_on("[email protected]:") depends_on("[email protected]:", when="@1.2:") depends_on("[email protected]:", when="@1.4:") # forward compatibility with Python depends_on("python@:3.12", when="@:1.10") depends_on("python@:3.13", when="@:1.12") depends_on("python@:3.14") ``` is better than disjoint when ranges causing repetition of the rules on dependencies, and requiring frequent editing of existing lines after new releases are done: ```python depends_on("[email protected]:3.12", when="@:1.1") depends_on("[email protected]:3.12", when="@1.2:1.3") depends_on("[email protected]:3.12", when="@1.4:1.10") depends_on("[email protected]:3.13", when="@1.11:1.12") depends_on("[email protected]:3.14", when="@1.13:")
haampie
added a commit
that referenced
this pull request
Nov 18, 2024
…ess common cases (#47402) The idea is to go from most to least used: backward compat -> forward compat -> pinning on major or major.minor version -> pinning specific, concrete versions. Further, the following ```python # backward compatibility with Python depends_on("[email protected]:") depends_on("[email protected]:", when="@1.2:") depends_on("[email protected]:", when="@1.4:") # forward compatibility with Python depends_on("python@:3.12", when="@:1.10") depends_on("python@:3.13", when="@:1.12") depends_on("python@:3.14") ``` is better than disjoint when ranges causing repetition of the rules on dependencies, and requiring frequent editing of existing lines after new releases are done: ```python depends_on("[email protected]:3.12", when="@:1.1") depends_on("[email protected]:3.12", when="@1.2:1.3") depends_on("[email protected]:3.12", when="@1.4:1.10") depends_on("[email protected]:3.13", when="@1.11:1.12") depends_on("[email protected]:3.14", when="@1.13:")
This was referenced Nov 25, 2024
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.
The idea is to go from most to least used: backward compat -> forward compat -> pinning on major or major.minor version -> pinning specific, concrete versions.
Further, imo the following
is better than disjoint when ranges causing repetition of the rules on dependencies, and requiring frequent editing of existing lines after new releases are done: