-
Notifications
You must be signed in to change notification settings - Fork 88
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
Latest wheel==0.32.0 breaks multibuild/supported_wheels.py #202
Comments
as temporary workaround, pinning wheel==0.31.1 in |
also delocate seems broken by wheel 0.32.0 (but you probably know that already) |
@matthew-brett I see you've opened an issue on the wheel repo, thanks for taking a look to quickly! 👍 |
Thanks for letting me know. I made a fix on the |
thanks, I'll try |
it's now failing with
I'll pin to 0.31.1 for now. |
travis build log with full traceback here: |
Oh man, they've really gone to town on refactoring the API. I think the official |
Seeing this on a Mac build:
https://travis-ci.org/hugovk/pillow-wheels/jobs/435064485#L4899 |
Yes, sorry, the API for wheel has completely changed, wreaking havoc with delocate, in particular. I'm working on it now. |
|
Chuck - thanks - yes - but the wheel folks have done a huge refactoring of their internals, so it's much worse than just a moved import, sadly. |
If |
Hi @matthew-brett , I'm feeling your pain :) The easiest short term fix is probably to pin the release version. |
It exists as (1) a setuptools extension and (2) a command line tool, according to the README: |
The latest devel of multibuild is now passing for Linux, and as expected Mac builds are failing due to delocate: https://travis-ci.org/python-pillow/pillow-wheels/builds/435238329 We're due for a quarterly Pillow release tomorrow (2018-09-01). Is delocate fixed in master, and if so, any chance of a release today or tomorrow? Or would it help if we tested it first, and is there anything else we can do to help? Thank you! |
Actually no rush, we're all good with pinning wheel (Linux and Mac) and I don't see anything really important where we would need the new wheel version. |
just noting that auditwheel is now failing as well (even after I set VIRTUALENV_NO_DOWNLOAD=1), as the manylinux docker images now ship with wheel 0.32.0 pypa/manylinux#228 https://travis-ci.org/fonttools/openstep-plist/jobs/435504919#L545 I have set wheel==0.31.1 in both BUILD_DEPENDS, TEST_DEPENDS, in pyproject.toml and have VIRTUALENV_NO_DOWNLOAD=1. |
See: pypa/manylinux#229 |
Thanks! |
@matthew-brett What is the status of this? Should we just go ahead and pin the wheel version? I'm looking to make a release next weekend. |
There's no harm in pinning, but it's not needed any more. |
Cool, thanks @matthew-brett. So is there anything keeping this issue open? |
@matthew-brett I assume we need to update the multibuild submodule hash? |
Yes, it should be latest |
From the latest Travis build it looks like we're using a very old `multibuild`: ``` Submodule path 'multibuild': checked out '7cca00d3d1d590a3ed34185ef1db1cd970c3a3a1' ``` I believe this will make sure the `submodule init` call gets the latest version which should fix the failure caused by https://github.com/matthew-brett/multibuild/issues/202
Closing, currently as far as I know all the pieces are in place to use the latest wheel version. Please reopen if I am mistaken. |
this was just released today: https://pypi.org/project/wheel/0.32.0/
the supported_wheels.py script in multibuild is now failing with the latest wheel version with this error:
https://travis-ci.org/fonttools/openstep-plist/jobs/435053641#L590
The text was updated successfully, but these errors were encountered: