Repository navigation
doc: Update RFC 8 on the minimal Python version in addons - #7691
Open
wenzeslaus wants to merge 2 commits into
Open
wenzeslaus wants to merge 2 commits into
wenzeslaus wants to merge 2 commits into
Conversation
github-actions
Bot
added
RFC
petrasovaa
previously approved these changes
Jul 14, 2026
Member
Author
|
While there is not an issue with new text, the example overall started to be confusing. |
wenzeslaus
force-pushed
the
rfc8-python-minimum
branch
from
July 15, 2026 22:07
2ba8c48 to
5b681bb
Compare
Addons need to work at least with the latest release and the development version, so their minimal Python version cannot be raised together with the development version. It needs to be raised only after the next release.
wenzeslaus
force-pushed
the
rfc8-python-minimum
branch
from
July 15, 2026 22:13
5b681bb to
66e0625
Compare
veroandreo
approved these changes
Jul 16, 2026
hellik
approved these changes
Aug 24, 2026
pesekon2
approved these changes
Aug 29, 2026
Member
|
Ws this motion passed at the last PSC meeting? |
Member
Still open as not all PSC members voted |
neteler
approved these changes
Nov 4, 2026
nilason
approved these changes
Nov 4, 2026
petrasovaa
approved these changes
Nov 5, 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
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.
RFC 8 currently says that the minimal Python version is raised for GRASS and for a matching branch in grass-addons at the same time. This does not work: addons need to work at least with the latest release and the development version, so their minimal Python version has to stay at what the latest release supports. Raising it together with the development version would break addons for users of the latest release.
The RFC is now modified to state that the minimal Python version in grass-addons is raised only after the next release, and adjusts the example accordingly. The rule for GRASS itself is unchanged.
The current situation is little more complicated, because we keep 8.4 supported for addons. This can re-occur for different reasons, hence the RFC text says "need to work at least with..."
AI (Claude Code with Opus) was used to prepare this change.