Recipe for Python part of Apache Arrow - #1732
Conversation
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/pyarrow:
|
| version: {{ version }} | ||
|
|
||
| source: | ||
| git_url: https://github.com/apache/arrow.git |
There was a problem hiding this comment.
Yes. If you could make those changes it will make this clearer.
There was a problem hiding this comment.
done, will wait for #992 to become feedstock then get this to a green build
|
The build and dependencies LGTM. |
daaffca to
0b7593d
Compare
|
This is failing because of PARQUET-747. I will update the parquet-cpp build and report back when this build is green |
|
OK, the parquet-cpp conda-forge package has been updated, looks like we're good to go whenever the OS X build passes |
| number: 0 | ||
| rpaths: | ||
| - lib # [unix] | ||
| - lib/python{{environ.get('PY_VER')}}/site-packages/pyarrow # [unix] |
There was a problem hiding this comment.
The linter is failing here. Would {{ environ['PY_VER'] + '*' }} work instead? That is known to pass.
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
@ocefpaf nope, that broke my rpath. trying again without the |
No problem. We should probably fix the linter and not the recipe anyways. |
|
This is good to go once the build is green |
|
Argh, well we have an rpath issue on OS X now. Looking. |
|
@ocefpaf I'm pretty bewildered by the OS X rpath stuff, do you have any advice? Our package builds on our Travis CI are working for OS X, e.g. https://travis-ci.org/apache/arrow/jobs/166942076 The issue here is that there is a C++ shared library nested under |
Sorry, never used a Mac in my life. Maybe @msarahan can help here.
Are you building with conda there? Note that the xcode is different too, but I don't think that is the issue.
I maintain this recipe where we had to manually change paths with |
|
I'm trying to resolve this in apache/arrow#171, setting this to build from that PR |
|
@wesm |
|
Let me see if this commit fixed it, and if not I'll make this Linux only to go to feedstock |
|
@msarahan @ocefpaf @jakirkham this problem appears to be localized to the old version of XCode being used in conda-forge -- I left a comment on the bigger discussion about OS X architecture |
|
@ocefpaf I disabled all but Linux for now, I can re-enable OS X when the XCode toolchain issues are resolved. thanks! |
|
Linux is no longer 😒 import: 'pyarrow'
Traceback (most recent call last):
File "/staged-recipes/build_artefacts/test-tmp_dir/run_test.py", line 26, in <module>
import pyarrow
File "/opt/conda/envs/_test/lib/python3.5/site-packages/pyarrow/__init__.py", line 20, in <module>
import pyarrow.config
ImportError: /opt/conda/envs/_test/lib/python3.5/site-packages/pyarrow/../../../libparquet_arrow.so: undefined symbol: _ZN5arrow16PrimitiveBuilderINS_11BooleanTypeEE6FinishEv
TESTS FAILED: pyarrow-0.1.post-0 |
|
Visibility is such a pain! I will fix |
@wesm this kind of changes needs more discussion. In principle I am 👍 to that but we need to consensus as this change should happen everywhere. (In fact, for my local builds, I use homebrew's It would be nice if you, or someone in your group, could participate some of our meetings and request that item to be discussed. See https://conda-forge.hackpad.com/conda-forge-meetings-2YkV96cvxPG Maybe we could start by putting together a conda-forge-enhancement-proposal to move to a modern XCode. See https://github.com/conda-forge/conda-forge-enhancement-proposals |
|
Oh, actually this is because the parquet-cpp package is out of date, whoops. |
…ds but Linux until OS X toolchain issues resolved
|
@ocefpaf looks like something is broken in the conda forge toolchain now? |
Good old "turn it off and on again" seems to fix it 😄 I re-started |
|
thank you! |
Requires #1729 and #992