MNT Set pyamg version following our bumping rules #31089
Merged
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.
4.2.0 is not available on conda-forge so I went for 4.2.1. I guess this falls under "there will be some exceptions sometimes" rule. We could install pyamg 4.2.0 with pip but I don't think this is worth the additional small complexity.
To be honest we may want to have 8000 a rule for core dependencies like numpy, scipy, pandas, matplotlib and another one for less core dependencies but I'll defer this to a separate issue.
This also fixes the fact that we were actually not testing against our minimum
pyamg
version.See #30895 (comment) for more context.
Related to #30888. It was an oversight in #30895.