You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/01/31 21:29:59 UTC
[GitHub] [arrow-datafusion] alamb edited a comment on pull request #1711: Add tests and CI for optional pyarrow module
alamb edited a comment on pull request #1711:
URL: https://github.com/apache/arrow-datafusion/pull/1711#issuecomment-1026230116
I also tried
```shell
PYO3_PRINT_CONFIG=1 PYO3_PYTHON=$(which python) cargo test --features=pyarrow -p datafusion -- pyarrow
error: failed to run custom build command for `pyo3 v0.15.1`
Caused by:
process didn't exit successfully: `/Users/alamb/Software/arrow-datafusion/target/debug/build/pyo3-0d2dc5a0a08d5a5d/build-script-build` (exit status: 101)
--- stdout
cargo:rerun-if-env-changed=PYO3_CROSS
cargo:rerun-if-env-changed=PYO3_CROSS_LIB_DIR
cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_VERSION
cargo:rerun-if-env-changed=PYO3_PRINT_CONFIG
-- PYO3_PRINT_CONFIG=1 is set, printing configuration and halting compile --
implementation=CPython
version=3.9
shared=true
abi3=false
lib_name=python3.9
lib_dir=/usr/local/opt/python@3.9/Frameworks/Python.framework/Versions/3.9/lib
executable=/Users/alamb/Software/virtual_envs/arrow_dev/bin/python
pointer_width=64
build_flags=WITH_THREAD
suppress_build_script_link_lines=false
```
So it seems like maybe pyo3 is picking up the right executable (my virtual env) but not the correct libdir 🤔
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org