Don't use outdated pre-release spaCy 4 #90
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
spaCy 4 hasn't been released. 4.0.0.dev{1,2} have been yanked,
questioning the stability. More importantly, 4.0.0.dev3 was published
2024-04-22 while the normal 3.8.7 is newer, being published 2025-05-23,
a whole year later. The outdated 2024 spaCy depends on an outdated
thinc, which depends on an outdated blis whose build fails on Python
3.13.
I fixed this by restricting spaCy to stable 3.x versions. The spaCy 4
apparently wasn't even being used in the final installation that Kokoro
sees, somehow only appearing in a misconfigured build step.
Fixes: hexgrad#85 (comment)
Reported-by: @cclauss
cclauss
approved these changes
Aug 31, 2025
cclauss
added a commit
to cclauss/misaki
that referenced
this pull request
Aug 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
spaCy 4 hasn't been released. 4.0.0.dev{1,2} have been yanked, questioning the stability. More importantly, 4.0.0.dev3 was published 2024-04-22 while the normal 3.8.7 is newer, being published 2025-05-23, a whole year later. The outdated 2024 spaCy depends on an outdated thinc, which depends on an outdated blis whose build fails on Python 3.13.
I fixed this by restricting spaCy to stable 3.x versions. The spaCy 4 apparently wasn't even being used in the final installation that Kokoro sees, somehow only appearing in a misconfigured build step.
Fixes: #85 (comment)
Reported-by: @cclauss