[ 
https://issues.apache.org/jira/browse/ARROW-17771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17606519#comment-17606519
 ] 

H. Vetinari commented on ARROW-17771:
-------------------------------------

> Could the issue be that Arrow DLLs and Arrow Python (PyArrow C++) DLL are in 
> a different location?

Yes, it sounds like the new location of the Arrow Python DLL is not taken into 
account (curious that it's still found with the ENABLE-stuff).

In any case, from the POV of conda-forge (i.e. when we get around to packaging 
the next released version), this would probably get installed somewhere in 
{{site-packages/arrow/...}}. I think it might be best to open a PR to the 
arrow-cpp-feedstock that points to the current master here (use {{git_url:}} 
etc., I can help if necessary), and we can figure out what needs to be done 
(either on the build script side or through patches) so that this runs through.

> [Python] Python does not finds the DLLs correctly on Windows
> ------------------------------------------------------------
>
>                 Key: ARROW-17771
>                 URL: https://issues.apache.org/jira/browse/ARROW-17771
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Python
>            Reporter: Alenka Frim
>            Priority: Critical
>             Fix For: 10.0.0
>
>
> It seems that after the Python refactoring PR 
> [https://github.com/apache/arrow/pull/13311] Python is unable to find 
> {{arrow_python}} even though the library it is imported into the correct 
> directory.
> Currently this issue is fixed with setting an additional environment variable:
> {code:}
> CONDA_DLL_SEARCH_MODIFICATION_ENABLE=1
> {code}
> We need to investigate further why this error is happening after the 
> [refactoring|https://github.com/apache/arrow/pull/13311] and make sure Python 
> is able to find the libraries on Windows without the additional env vars 
> being specified.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to