Actually use build-constraints.txt #26
Merged
Conversation
This file contains 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
Use the build-constraints.txt file when building all repos, to avoid using numpy 2 which can break spacy.
|
Going to merge, and will retrigger a few workflows in various repos just to make sure it doesn't break anything. |
This was referenced Jun 17, 2024
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.
Use the build-constraints.txt file when building all repos, to avoid using numpy 2 which can break spacy.
Continues on the work done in #25.
Keeping this a branch and testing on SuffolkLITLab/FormFyxer#136, until I can confirm that this fixes the issue seen there. Will merge once it does.