You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (Jira)" <ji...@apache.org> on 2020/03/05 19:42:00 UTC
[jira] [Commented] (ARROW-8015) [Python] Build 0.16.0 wheel install
for Windows + Python 3.5 and publish to PyPI
[ https://issues.apache.org/jira/browse/ARROW-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052466#comment-17052466 ]
Wes McKinney commented on ARROW-8015:
-------------------------------------
We don't need ursabot to build the wheel. It would be good to run all the unit tests on Windows on Python 3.5 to make sure something isn't broken there. I can't look at it today but if someone else with a properly configured Windows VM or machine can kick the tires and provide a wheel someone with write access to PyPI can upload it
> [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
> 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)