-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] venv created by uv works not well with pyo3 #12343
Comments
Got similar error, and solved by manually copy the dll into the Scripts folder. It surely requires a copy or hard link to python dll. |
cc @geofft |
Same exact issue here, on multiple Mac machines: I'm compiling a C++ project using CMake, with the following script:
CMake correctly identifies the CPython library in
One weird thing is that on one mac everything seems to work correctly, but that mac doesn't have a root |
@Svalorzen for mac you could see this PR https://github.com/astral-sh/uv/pull/10629/files#diff-59b5f06938f826cd9b0657938f1cb0b1f2f112b2fb0689bee13ae918d5538820R514-R534 |
@Svalorzen please open a new issue instead of adding a different case to an existing one |
Summary
Like #10598, when build project using pyo3 with uv-managed python, but for windows.
It would build successfully but could not run since no python.dll found
env:
log for build
dependencies of built exe
Shall we copy
python313.dll
to.env/Scripts
like whatpython -m venv .venv
does (see also pypa/virtualenv#1050 (comment))Platform
Windows 11 x86_64
Version
0.6.0
Python version
Python 3.13.2
The text was updated successfully, but these errors were encountered: