-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error installing: ValueError: numpy.dtype size changed
#135
Comments
An example of the build failure: https://github.com/SuffolkLITLab/FormFyxer/actions/runs/9540258846/job/26291740248?pr=136 |
Figured out a local fix: from the thinc docs, you can specify build constraints. I think since we're running spacy while building/installing formfyxer, the normal fix of "just use numpy<2.0.0" doesn't work because of how pip installs dependencies when building packages. Can't fully articulate, but if you run: PIP_CONSTRAINT=build-constraints.txt pip install . --no-cache-dir with
it works. Happy to hear additional approaches, but I think the best way to fix this at the moment is to patch |
Okay, with SuffolkLITLab/ALActions#26, this should be fixed on CI/CD. Not sure if we should add something to the docs saying that TBH, I'm sure this will start affecting a few people come this week, and spacy and thinc might come up with better workarounds, so I might keep this open just to wait for those. |
Having a lot of trouble installing FormFyxer on a fresh virtual env. Below is the error
Related to explosion/spaCy#13528, but I seem to be having the same error when I fix the version of numpy to below 2.0.0. Not sure why the obvious fix isn't working, but pip runs all of it in a temporary dir that gets deleted, so I can't see what actual code is being run there.
Workaround is just to remove the entire
InstallSpacyModelCommand
:FormFyxer/setup.py
Lines 9 to 14 in fce8447
That workaround won't fly for our situation, but I'll have to see if it breaks our GH actions as well, or if it's just on my machine.
The text was updated successfully, but these errors were encountered: