Closed clin1234 closed 5 months ago
But I have the build tools installed. In fact, I was running it from the Developer Command Prompt for VS 2022
Setuptools is reporting that it can't find vcvarsall.bat... I have a memory that microsoft stopped using vcvarsall.bat to set up its build environments, but I don't know why setuptools would be insisting on that file existing. Maybe try upgrading setuptools?
setuptools is already at the latest version: 70.1.0
~Tracking: https://github.com/pypa/setuptools/issues/4431~
Update:
"C:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Tools\MSVC\14.41.33923\bin\HostX86\x64\link.exe" /nologo /INCREMENTAL:NO /LTCG /DLL /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO /LIBPATH:C:\Users\ךינשגכהד\scoop\apps\python-alpha\current\libs /LIBPATH:C:\Users\ךינשגכהד\scoop\apps\python-alpha\current /LIBPATH:C:\Users\ךינשגכהד\scoop\apps\python-alpha\current\PCbuild\amd64 "/LIBPATH:C:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Tools\MSVC\14.41.33923\lib\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.26100.0\ucrt\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\\lib\10.0.26100.0\\um\x64" "/LIBPATH:C:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Tools\MSVC\14.41.33923\lib\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.26100.0\ucrt\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\\lib\10.0.26100.0\\um\x64" /EXPORT:PyInit__cffi_backend build\temp.win-amd64-cpython-313\Release\src/c/_cffi_backend.obj build\temp.win-amd64-cpython-313\Release\src/c/libffi_x86_x64\ffi.obj build\temp.win-amd64-cpython-313\Release\src/c/libffi_x86_x64\prep_cif.obj build\temp.win-amd64-cpython-313\Release\src/c/libffi_x86_x64\types.obj /OUT:build\lib.win-amd64-cpython-313\_cffi_backend.cp313-win_amd64.pyd /IMPLIB:build\temp.win-amd64-cpython-313\Release\src/c\_cffi_backend.cp313-win_amd64.lib src/c/libffi_x86_x64\win64.obj
Creating library build\temp.win-amd64-cpython-313\Release\src/c\_cffi_backend.cp313-win_amd64.lib and object build\temp.win-amd64-cpython-313\Release\src/c\_cffi_backend.cp313-win_amd64.exp
_cffi_backend.obj : error LNK2001: unresolved external symbol _PyErr_WriteUnraisableMsg
build\lib.win-amd64-cpython-313\_cffi_backend.cp313-win_amd64.pyd : fatal error LNK1120: 1 unresolved externals
error: command 'C:\\Program Files\\Microsoft Visual Studio\\2022\\Preview\\VC\\Tools\\MSVC\\14.41.33923\\bin\\HostX86\\x64\\link.exe' failed with exit code 1120
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for cffi
Failed to build cffi
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (cffi)
[end of output]
Fixed by bumping cffi
to https://github.com/python-cffi/cffi/releases/tag/v1.17.0rc1
?
If you have a pyvex issue please let us know, this issue appears resolved.
If you have a pyvex issue please let us know, this issue appears resolved.
I'm bewildered because the prerelease version of cffi hasn't been published to PyPI yet, as far as I can tell. Without bumping the cffi version in pyproject.toml, on 3.13, building from source will fail
We don't support unreleased python versions. cffi has published their rc to PyPI but it is a pre-release so pip will select the latest stable instead. Once 3.13 is officially released and cffi's support is stable, we can revisit it, but I don't anticipate any changes will be needed on the pyvex side, as pip will automatically select the latest version of cffi anyways.
Description
Running the install command with 3.13 yielded the following
Steps to reproduce the bug
No response
Environment
No response
Additional context
No response