amoeba commented on issue #45530: URL: https://github.com/apache/arrow/issues/45530#issuecomment-2719398840
I found a local fix but I'm not sure what tweak we need to make to make it real. If I copy the delvewheel-mangled msvcp140.dll DLL from the inside the wheel we built on CI into the pyarrow install dir (`$venv\\Lib\\site-packages\\pyarrow`), the test passes. I'm fairly sure we do need to keep msvcp140.dll around so we must have broken something there. I don't know how python decides what files to include when a wheel is installed but I'm guessing that's my next step. <details> <summary>Full set of steps I ran for the curious</summary> 1. Download a wheel that exhibits the behavior from https://github.com/ursacomputing/crossbow/actions/runs/13303559126/job/37149410875 (Python 3.13 amd64 in this case) ```sh $ python -m venv venv $ .\venv\Scripts\Activate.ps1 $ pip install -r C:\Users\Bryce\Source\apache\arrow\python\requirements-build.txt $ pip install -r C:\Users\Bryce\Source\apache\arrow\python\requirements-wheel-test.txt $ pip install .\pyarrow-20.0.0.dev88-cp313-cp313-win_amd64.whl $ python -m pytest --pyargs pyarrow -k cython $ # notice the cython tests fail here with The specified module could not be found. $ # next step is done in wsl since I have no idea how to rename files in powershell $ unzip pyarrow-20.0.0.dev88-cp313-cp313-win_amd64.whl -d unzipped $ cp .\unzipped\pyarrow.libs\msvcp140-a4b2ab3dc6cde85d4f2c0e24432d66e1.dll C:\\Users\\Bryce\\Downloads\\wheel\\venv\\Lib\\site-packages\\pyarrow\\ $ # cython tests now pass ``` C:\\Users\\Bryce\\Downloads\\wheel\\venv\\Lib\\site-packages\\pyarrow </details> -- 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-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
