amoeba commented on PR #46079: URL: https://github.com/apache/arrow/pull/46079#issuecomment-2791317402
I had hoped to exercise the new helper code (I still can) but I figured something out that makes me think we can just merge this as-is. The skip is actually because "Python not available" not because we fail the version check as I had hoped. This happens due to what appears to be a bug in reticulate which is confusing because it's a very basic thing to have not work. The code in this PR uses `reticulate::py_discover_config()` which claims to tell us what reticulate will find when it goes looking for a Python installation. The documentation claims it follows [Order of Discovery](https://rstudio.github.io/reticulate/articles/versions.html#order-of-discovery) which, if you read all the way through, item 15 says it will search the `PATH` for `python` or `python3`. However, in a VM with R and `python3` in the PATH, I get, ``` > py_discover_config() NULL ``` This seems to be a bug and may explain why none of our CI jobs actually run the reticulate tests @jonkeane. If I explicitly tell reticulate which Python to use, this new helper works fine, ``` > Sys.setenv("RETICULATE_PYTHON"="/usr/bin/python3") > py_discover_config() python: /usr/bin/python3 libpython: /usr/lib/python3.12/config-3.12-aarch64-linux-gnu/libpython3.12.so pythonhome: //usr://usr version: 3.12.7 (main, Feb 4 2025, 14:46:03) [GCC 14.2.0] numpy: [NOT FOUND] ``` -- 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]
