MAINT: synchronize meson version requirements - #862
Merged
Conversation
dnicolodi
force-pushed
the
fix/meson-version-check
branch
from
July 2, 2026 08:09
86a90ea to
24cc41a
Compare
Make the runtime version check the same as the dependency declaration
in pyproject.toml and add a test to verify the equivalence.
Requiring 0.64 over 0.63.3 was mostly a cosmetic change to allow to
write `import('python').find_installation(pure: false)` in the test
packages, thus the runtime version check was not update in sync to
allow to use the older meson for a while longer in special settings.
The old meson version should have been retired by now, and keeping the
version checks consistent is less confusing.
dnicolodi
force-pushed
the
fix/meson-version-check
branch
from
July 2, 2026 08:11
24cc41a to
fc5faa7
Compare
rgommers
added
the
maintenance
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
3 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.
Make the runtime version check the same as the dependency declaration in pyproject.toml and add a test to verify the equivalence.
Requiring 0.64 over 0.63.3 was mostly a cosmetic change to allow to write
import('python').find_installation(pure: false)in the test packages, thus the runtime version check was not update in sync to allow to use the older meson for a while longer in special settings. The old meson version should have been retired by now, and keeping the version checks consistent is less confusing.xref gh-861