[ https://issues.apache.org/jira/browse/ARROW-10777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kouhei Sutou resolved ARROW-10777. ---------------------------------- Fix Version/s: 3.0.0 Resolution: Fixed Issue resolved by pull request 9145 [https://github.com/apache/arrow/pull/9145] > [Packaging][Python] PyPI pyarrow source dist (sdist) contains architecture > dependent binaries > ---------------------------------------------------------------------------------------------- > > Key: ARROW-10777 > URL: https://issues.apache.org/jira/browse/ARROW-10777 > Project: Apache Arrow > Issue Type: Bug > Components: Packaging, Python > Affects Versions: 2.0.0 > Reporter: Daniel Jewell > Assignee: Kouhei Sutou > Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 2h > Remaining Estimate: 0h > > Downloading the most recent pyarrow "sdist" *source* tarball from Pypi and > upon extraction, the package contains multiple *binary* libraries compiled > for x86-64. (libarrow, libparquet, etc.) > > The ultimate result is that this isn't a source package at all - it would be > fine to include binaries in a python wheel but including arch/platform > specific binaries in a sdist breaks pip and the install. (In my case, trying > to install on aarch64.) > As a general observation, this will become a larger issue as, for example, > the ARM-based Macs come to market. > That said, one commonly implemented option is to make the python source > package download and build any dependent libraries. > > At the very least, the source package should not contain binaries. I suppose > it's not much different from a *source* Debian package containing compiled > binary code. > -- This message was sent by Atlassian Jira (v8.3.4#803005)