You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the PyPI releases page (https://pypi.org/project/deltalake/0.6.4/#files), the arm64 wheel file is published as deltalake-0.6.4-cp37-abi3-macosx_10_9_arm64.whl. However, it should be macosx_11_0_arm64.whl. This causes pip to not install from source instead of using the pre-built wheel.
What you expected to happen: Pip should install from wheel.
More details:
Note that pip -v debug does not contain macosx_10_9_arm64 but does contain macosx_11_0_arm64. As such, macosx_10_9_arm64 is never a compatible ABI tag. I believe the actions release workflow is not generating the correct ABI tag.
…sal2 wheel (#976)
# Description
- Add a new Python binding release Github Action for `universal2` wheel
in PyPy
- Set version 1 for maturin-action
# Related Issue(s)
- closes#972
# Documentation
- **universal2:**
This wheel contains both architectures, causing it to be up to twice the
size (data files do not get doubled, only compiled code). It requires
Pip 20.3 (Packaging 20.6+) to load on Intel, and Pip 21.0.1 (Packaging
20.9+) to load on Apple Silicon.
Environment
Binding: Python
Environment:
Bug
What happened:
On the PyPI releases page (https://pypi.org/project/deltalake/0.6.4/#files), the arm64 wheel file is published as
deltalake-0.6.4-cp37-abi3-macosx_10_9_arm64.whl
. However, it should bemacosx_11_0_arm64.whl
. This causes pip to not install from source instead of using the pre-built wheel.What you expected to happen: Pip should install from wheel.
More details:
Note that
pip -v debug
does not containmacosx_10_9_arm64
but does containmacosx_11_0_arm64
. As such,macosx_10_9_arm64
is never a compatible ABI tag. I believe the actions release workflow is not generating the correct ABI tag.Release log: https://github.com/delta-io/delta-rs/actions/runs/3567491762/jobs/5995258547#step:3:668
Possible fixes
The text was updated successfully, but these errors were encountered: