-
Notifications
You must be signed in to change notification settings - Fork 23
MAINT: Try making 3.10 wheels on Windows and OSX #135
Conversation
23ad949
to
a06b1c5
Compare
close/reopen |
c54de02
to
9463e8f
Compare
f469a97
to
b47efc1
Compare
Two things are new with the 3.10 release
|
I wonder if cibuildwheel + github actions will be any different. |
For 32-bit windows wheels, if all else fails we might be able to use a 32-bit docker container image, and then run it via a container |
It seems cibuildwheel has 32-bit windows, see the table of supported versions |
@mattip, the omission of 32 bit Python 3.10 on windows was a deliberate choice of the azure folks. We could probably talk them into it, but if Microsoft is headed that way, we might want to go along. The bigger problem is that travis-ci has become completely unreliable for arm64, mostly timeouts on fetches and downloads. I don't know the cause, but it is a PITA. |
If so, the Azure folks should talk to their own CPython expert - who seems to think that 32-bit will be around for a while : scipy/scipy#14316 (comment) |
@matthew-brett See actions/runner-images#4226 (comment). I do have a question about multibuild, it won't build Python 3.10 wheels for x86_64, only for arm64 and universal2 wheels. I'm not sure if those wheels work correctly. I think this is due to line 168 in osx_utils.sh. Maybe the mac version number needs an update to |
|
@charris - sorry for my confusion - but here's my understanding:
So, I was expecting x86_64 builds to work for Python 3.10; does they fail? Is there any error to look at somewhere? Happy to fix ASAP if they don't work. |
Well, I don't know if they do or not. The universal2 file is big enough, but I'd like to see it checked before a release. Multibuild does produce separate arm64 (macosx_11_0) wheels, but no x86_64 wheels. I'm not really clear on why not, nor what it means that 3.10 only supports universal2 wheels. |
No description provided.