Closed percevalw closed 1 month ago
There was a problem with the metadata on that release. It shouldn't list support for older Pythons. I've yanked the release and am rebuilding.
Python only allows you to have one version of each library in the tree at once, and spaCy cannot support both numpy v1 and numpy v2 as they're binary incompatible. We need to update the pin to allow people to use spaCy with other libraries that require numpy v2. If numpy v2 doesn't support Python 3.8, this means spaCy can't support it either.
The only solution is to update your Python, or continue using the version of spaCy that's been working for you.
Python versions release every year now, which means the build matrix will grow quickly for libraries like numpy and spaCy that need to build wheels for each version of Python. This means libraries have to prune support for older Pythons, and you'll need to update your Python version periodically in order to keep using new library releases in the ML/data stack.
New release v3.8 is up, which should fix the problem.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
How to reproduce the behaviour
Hi, it seems that the latest spacy release has bumped the numpy build dependency:
(from pyproject.toml in the pypi source distribution)
These requirements are not the same as the one on the main branch of your repo: https://github.com/explosion/spaCy/blob/30f1f33e78e123d8ba9cf10ee8edb98a5a5e7170/pyproject.toml#L1C1-L12C40
breaking installations for earlier python versions (I think numpy 2.0 is only py > 3.10 ?), see below:
Your Environment