jorisvandenbossche commented on issue #44991:
URL: https://github.com/apache/arrow/issues/44991#issuecomment-2534559191

   Not that this explains why it would have started failing now, but we should 
probably also "modernize" the way we install pyarrow here. 
   It's still using `python setup.py develop`, and then testing the installed 
package (`pytest --pyargs pyarrow.tests` and not `pytest pyarrow/tests`) but 
from within the `arrow/python` directory, where it might also pick up the 
inplace build? And @pitrou you show that the lib exists in 
`C:\Miniconda38-x64\envs\arrow\lib\site-packages\pyarrow`, but so that is not 
inplace? (or does the `dir` cmd follow the `pyarrow.egg-link`?)


-- 
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]

Reply via email to