-
Notifications
You must be signed in to change notification settings - Fork 64
LNK1104: cannot open file 'python3.lib'
in Windows Python 3.13 RC
#864
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
Comments
Can you check if |
I could reproduce it from local Windows PC, so it's not problem of And same error occurs in abi3_pyproject_ext example of scikit-build-core. So it's not problem of nanobind. |
Oh, ok, let me add this to the test cases to try and reproduce here as well |
Still it is most probably a CMake issue, but I couldn't find any reports in the [upstream issues](https://gitlab.kitware.com/cmake/cmake/-/issues. Managed to capture the test failure in |
Even if it is, we likely can fix it via setting |
Debugging in #865 |
I have a feeling we are being affected by python/cpython#110049 combined with some logic issues, some of these variables were missing on Windows before. |
Looks like that fixes our tests, at least. |
Should be fixed in 0.10.4! |
Fix confirmed! Thank you 👍 |
Build fails when targeting ABI3 with Windows + Python 3.13.
OS: Windows
Python: 3.13.0rc1
Full log: https://github.com/dofuuz/nanobind_example/actions/runs/10452840733/job/28942106258#step:5:96
Source: https://github.com/dofuuz/nanobind_example/tree/43c312cfa2dba30183c66a1f8b5ed31c8e0b8083
python3.lib exists within Python libs folder.
More simple way to reproduce it from scikit-build-core example:
The text was updated successfully, but these errors were encountered: