setup: Bump numpy version to equivalent to 2.1 #144
Conversation
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
On investigation, it doesn't seem like drawsvg uses anything specific to 1.16+'s APIs, so it's worth a try.
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.
On further investigation, it appears numpy usage is limited to parts of the API that have not changed since 1.16, so I forked and updated the dependency and validated it was now working (at least as far as generating an SVG and then rasterising it to PNG).
This change does mean that the oldest version of Python this can be compatible with is Python 3.10, while the older dependency,
~= 1.16seems to allow compatibility with Python 2.7 to 3.12, so please feel free to reject this PR.Closes #143