temporary pin uber/h3-py to avoid 4.x breaking behaviour #1157
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.
🚀 Pull Request
Description
This pull-requeste introduces a temporary pin to
h3-py ==3.7.7
in order to avoid breaking behaviour introduced in 4.1.0.Weirdly they appear to have skipped the 4.0.0 release 😕
Merging this pin to
main
will unblock thepyvista
integration workflow. We can then fix and patchgeovista
(introducing a minimum pin) to work withh3-py
>=4.x
Note that, this breaking behaviour only appears to happen with PyPI dependencies, which install 4.x, whereas the
conda
lock files don't resolve for 4.x and instead remain with the working 3.7.7.Hence why the
ci-locks-test
workflow didn't trip 😠