vwbusguy commented on issue #36965:
URL: https://github.com/apache/arrow/issues/36965#issuecomment-1659441303
Looks like this error is actually happening when installing gluonts, which
was bringing in pyarrow. Installing pyarrow standalone seems to work just fine
with either pip or conda, but it seems installing gluonts from pip tries to
*build* pyarrow even if pyarrow already exists where installing it through
conda-forge is content to use the existing binary.
More curious, the build this morning pulled the wheel directly:
```
Collecting pyarrow~=8.0
Downloading
pyarrow-8.0.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (29.4
MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 29.4/29.4 MB 289.0 MB/s eta
0:00:00
```
Where the builds as of this afternoon started pulling pyarrow in as a
tar.gz. Seems like perhaps something has happened in PyPi land today and now
the source is being downloaded instead of the binary?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
