-
-
Notifications
You must be signed in to change notification settings - Fork 160
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
Install fails to build on Python 3.13 #217
Comments
I haven't had the chance to figure out why the build is failing on Windows yet, which is holding up the release. |
Any progress on this? Is there a way to build for windows yet, for python 3.13? |
No, I don't have access to a Windows system to test so sort of at the whim of GitHub Actions, if someone wants to work on this it'd be welcome! |
ok, I've never used rust or maturin before, but I'll give it a go |
ok, it said: Wheel then installs ok on python 3.13 First time success. Built on windows 10, python 3.13. That's good, right? Should I be trying some profile other than dev? |
So, the release profile built ok too, once I realised I just needed to run Maybe it was because I was compiling using python 3.13, maybe because it was a very clean new install of both rust and maturin, but there were no warnings or hiccups. |
Ah, I think this is the underlying problem: PyO3/maturin-action#292 (comment)
|
fix for jamesturk#217
thanks for this, release was pushed! |
I'm only seeing Windows 3.9 support for the compiled builds on the files for 1.1.2, which is the most recent release. |
@jamesturk that is odd - I'm seeing the same as tswast - the windows py-3.13 build goes fine, but it doesn't get uploaded to pypi.org upon release. I've never uploaded to pypi, so I don't know what's going on here, but it seems a strange thing, and it means that lots of users still won't be able to use jellyfish on python 3.13 on windows. |
ok, I think this should fix it #223 |
Basically same as #199
Python 3.13.0 just released, and there is no prebuilt packages for it, I guess.
The text was updated successfully, but these errors were encountered: