-
Notifications
You must be signed in to change notification settings - Fork 22
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
Doesn't work with Python 3.10.1 #78
Comments
Please run this command and check its output. Any packages shown there must be reinstalled:
Especially if escrotum is included you have to rebuild it! |
Same issue here even after rebuilding all the 3.9 packages. |
Works fine for me. @SuperZoops |
Oh sorry, I fixed it after rebuilding all 3.10 packages, there was nothing in 3.9 before it broke though as I rebuilt everything as soon as 3.10 dropped, so something between 3.10 and 3.10.1 must have broken it. |
Yeah, that fixed. Why does this happens tho? I'm asking just to learn something, if you have any time to answer would be much appreciated. Thanks in advance! |
@kodenart |
Sure, but that's the first package that I've had to explicitly tell the manager to rebuild. Maybe there's some info missing in the dependencies area of the package? |
All official packages are rebuilt automatically. But AUR packages are your own responsibility. Especially VCS packages (-git) will only be bumped if their PKGBUILD changes (usually). |
Thx! |
After reading this issue:
#68
I was able to get escrotum working on python 3.10.1 again, however the issues I was having prior to installing escrotum as a python package and also installing python-numpy from AUR as mentioned as fix actions.. my issues were identical to the issues given when python upgraded to 3.9.
Everything from the original post in #68 is identical and relevant to the issue upgrading from python 3.9 to 3.10(.1), I am also running Arch Linux and I received the same exact errors.
As noted, installing python-numpy and running
pip install escrotum
have fixed the issue in the meantime.The text was updated successfully, but these errors were encountered: