[
https://issues.apache.org/jira/browse/ARROW-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056459#comment-17056459
]
Wes McKinney commented on ARROW-8015:
-------------------------------------
Here is a candidate 3.5 wheel that I built locally
https://drive.google.com/open?id=1_hvgnMafWOZSgPCldNjp6iIiW3tCLwvX
It doesn't have:
* Flight
* Gandiva
* Brotli, LZ4, or ZSTD (it has Snappy and ZLIB though)
I had to comment out some lines about bundling zlib.dll because with
{{-DZLIB_SOURCE=BUNDLED}}, zlib is statically linked with {{arrow.dll}}.
I tested out the wheel locally by running the Python test suite and it looks
good to me. I'll wait about 24 hours for feedback and then upload to PyPI is
all looks good
> [Python] Build 0.16.0 wheel install for Windows + Python 3.5 and publish to
> PyPI
> --------------------------------------------------------------------------------
>
> Key: ARROW-8015
> URL: https://issues.apache.org/jira/browse/ARROW-8015
> Project: Apache Arrow
> Issue Type: Improvement
> Reporter: Mark Keller
> Assignee: Wes McKinney
> Priority: Major
>
> Hi,
>
> I'd like to help getting {{pyarrow==0.16.0}} released for Windows Python 3.5.
> I have seen the issue here:
> [https://ci.appveyor.com/project/Ursa-Labs/crossbow/builds/27848124]
> I'm not familiar with your release build procedure, but I have been trying
> to follow
> [https://github.com/apache/arrow/blob/master/docs/source/developers/python.rst#building-on-windows]
> Note that I have replaced:
> {{conda create -y -n pyarrow-dev -c conda-forge ^
> --file arrow\ci\conda_env_cpp.yml ^
> --file arrow\ci\conda_env_python.yml ^
> --file arrow\ci\conda_env_gandiva.yml ^
> python=3.7}}
> with
> {{conda create -y -n pyarrow-dev -c conda-forge ^
> --file arrow\ci\conda_env_cpp.yml ^
> --file arrow\ci\conda_env_python.yml ^
> --file arrow\ci\conda_env_gandiva.yml ^
> python=3.5}}
> I also had to update {{Cython}} manually and that {{python setup.py
> build_ext --inplace}} seemed to do nothing, so I tried doing {{pip wheel -w
> dist .}} and this successfully built a wheel file for me.
> I understand that {{ursabot}} is down, but when it comes back could you retry
> building the missing wheel? It is possible that this dependency issue is
> already resolved.
> If I am wrong about the build procedure please let me know, I'm really
> unfamiliar with Windows development and your build procedure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
