CPython 3.11 wheels are not available on PyPI #342
Comments
|
@webknjaz Any ideas? Is it because it was built with prerelease=False here? |
|
Any updates on a release? I'm trying to install aiohttp. I cannot install the dependencies to build it myself. UPDATE: i made something that auto-builds it so I can get sutff quicker, so I no longer need this badly |
|
I presume there's no ETA until frozenlist updates wheels to sync with 3.11 changes? |
There is a transitiv dependency on frozenlist, which updated their package for python 3.11, but didn't add the package to pypi wheels. Thus, building on python >= 3.11 fails the whole docker building process ([issue](aio-libs/frozenlist#342)). Switching to python 3.10. Secondly, there are two more vulnerabilities due to cosign, which cannot be fixed on our side. Ignore listing them until cosign publishes a new version.
There is a transitiv dependency on frozenlist, which updated their package for python 3.11, but didn't add the package to pypi wheels. Thus, building on python >= 3.11 fails the whole docker building process ([issue](aio-libs/frozenlist#342)). Switching to python 3.10. Secondly, there are two more vulnerabilities due to cosign, which cannot be fixed on our side. Ignore listing them until cosign publishes a new version.
There is a transitiv dependency on frozenlist, which updated their package for python 3.11, but didn't add the package to pypi wheels. Thus, building on python >= 3.11 fails the whole docker building process ([issue](aio-libs/frozenlist#342)). Switching to python 3.10. Secondly, there are two more vulnerabilities due to cosign, which cannot be fixed on our side. Ignore listing them until cosign publishes a new version.
There is a transitiv dependency on frozenlist, which updated their package for python 3.11, but didn't add the package to pypi wheels. Thus, building on python >= 3.11 fails the whole docker building process ([issue](aio-libs/frozenlist#342)). Switching to python 3.10. Secondly, there are two more vulnerabilities due to cosign, which cannot be fixed on our side. Ignore listing them until cosign publishes a new version.
There is a transitiv dependency on frozenlist, which updated their package for python 3.11, but didn't add the package to pypi wheels. Thus, building on python >= 3.11 fails the whole docker building process ([issue](aio-libs/frozenlist#342)). Need to add gcc and libc to docker container as well as upgrade pip to resolve this. Secondly, there are two more vulnerabilities due to cosign, which cannot be fixed on our side. Ignore listing them until cosign publishes a new version.
There is a transitiv dependency on frozenlist, which updated their package for python 3.11, but didn't add the package to pypi wheels. Thus, building on python >= 3.11 fails the whole docker building process ([issue](aio-libs/frozenlist#342)). Need to add gcc and libc to docker container as well as upgrade pip to resolve this. Secondly, there are two more vulnerabilities due to cosign, which cannot be fixed on our side. Ignore listing them until cosign publishes a new version.
|
Seems like this is the case due to the CI workflow not running successfully: https://github.com/aio-libs/frozenlist/actions/runs/3391664330/jobs/5637039836 |
|
Version 1.3.3 has been released, which includes 3.11 wheels. |
|
Taking a look at the original issue a little closer, it appears that the default behaviour is to build for release candidates, and that builds for beta releases should not be deployed: https://cibuildwheel.readthedocs.io/en/stable/options/#prerelease-pythons The timing for the previous release was 6 days before the release candidate, so we just missed it. Will have to pay attention to that in future. |
|
Yep, I didn't want to release the wheels before the final release. And post that date, dependabot updating cibuildwheel enabled the Cython version automatically. Thanks for taking care of this! |
There was a problem with the frozenlist package, which didn't had its packages added to wheels (aio-libs/frozenlist#342). The packages are now added, so the fix for this can be reverted.
There was a problem with the frozenlist package, which didn't had its packages added to wheels (aio-libs/frozenlist#342). The packages are now added, so the fix for this can be reverted, except for the pytest job which is the only one building on a debian image (faster runtime). Here the yarl and multidict packages still have the same problem as frozenlist had. Waiting fo a fix here.
Long story short
While it appears based on a couple other issues that frozenlist has been updated to work with 3.11 in version 1.3.1, no 3.11 wheels were uploaded to PyPI. https://pypi.org/project/frozenlist/1.3.1/#files I understand that at the time of that release the 3.11 interfaces may not have been finalized so there may have been good reason not to publish them at that time.
Expected behaviour
Wheels are available for CPython 3.11 on PyPI.
Actual behaviour
Wheels are not available and must be built locally, even if this is done automatically.
Steps to reproduce
Look at https://pypi.org/project/frozenlist/1.3.1/#files and search for
cp311and note no search hits.Your environment
frozenlist is a transitive dependency that is not pinned for us and we operate on all platforms, Intel and ARM, and CPython 3.7 through 3.11.
The text was updated successfully, but these errors were encountered: