GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||
GeezerVison is showing github.com — Add support for Python 3.7 by lelit · Pull Request #73 · pypa/cibuildwheel Conversation
Contributor
This enables building binary wheels for Python 3.7, now at its rc1 release. It is included in the latest manylinux1 Docker image, see pypa/manylinux#196. Accordingly to https://www.appveyor.com/docs/build-environment/#python it is not yet available on Appveyor.
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
This enables building binary wheels for Python 3.7, now at its rc1 release. It is included in the latest manylinux1 Docker image, see pypa/manylinux#196. Accordingly to https://www.appveyor.com/docs/build-environment/#python it is not yet available on Appveyor.
Contributor
Author
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Contributor
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Contributor
Author
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
|
There was an error while loading. Please reload this page.
|
Nice! :-) EDIT: Personally, I don't care about dockcross that much, to be fair. It's mainly meant to test the alternative docker image option, so we can just temporarily disable that test, as far as I'm concerned. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Please, release this. Getting 3.7 builds building at rc1 stage means we can find more 3.7 bugs before the actual release. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Fair enough. Let's just temporarily disable that one test, then? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Fair enough. Let's just temporarily disable that one test, then?
Would be it any better if we just ignore/skip unavailable versions within a
given image? In that way, there would be less pressure on cibuildwheel to
follow whatever Docker image one is using (I mean for example the cases when
"imagexyz dropped Python 3.4"...).
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Myeah, but wouldn't you want to know by having that as an error and manually disabling that version for that build, instead of silently ignoring what could be a potential oversight? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Possibly yes... I was just thinking aloud (I do not use alternative manylinuxXX images myself): the question is about whether it should be always an hard error or if it could be downgraded (by default, or with an option) to a warning message instead. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Yes, no, sorry, didn't mean to shut that suggestion down completely, but just my 2 cents on that. Since |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
We'll reenable this when 3.7 is released and dockcross updates :)
|
Yeah, let's just disable that test on Python 3.7 for now then :) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
The 06_docker_images test is really just there to check that the CIBW_MANYLINUX1_XXX_IMAGE options are honored, it's up to the user to create a valid config. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Released as 0.9.0! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thank You! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Great, many thanks! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.