Skip to content
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

unable to compile pywin32 with python3.13 #2234

Closed
Battant opened this issue Mar 29, 2024 · 2 comments · Fixed by #2260
Closed

unable to compile pywin32 with python3.13 #2234

Battant opened this issue Mar 29, 2024 · 2 comments · Fixed by #2260

Comments

@Battant
Copy link

Battant commented Mar 29, 2024

Hello,

I try to compile pywin32 man branch with Python 3.13.0a5 with visual studio 2022 Community but i get this error 👍

win32/src/PyTime.cpp(280): error C3861: 'PyEval_CallObject' : identificateur not found

My Configuration 👍
Windows 11 pro
pxthon3.13a5

visual studio 2022 wiothh required packages

step to reproduce 👍
Downloud python3.13 onclone pywin32 repository
open a viisual studio 2022 prompt in pywin32 repository
run this commanand
`
python setup.py -q build

win32/src/PyTime.cpp(280): error C3861: 'PyEval_CallObject' : identificateur not found
error: command 'C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\bin\HostX86\x86\cl.exe' failed with exit code 2
'

Could you help me please to fix this issus

Best regards

Battant

@clin1234
Copy link
Contributor

Same here. There are several instances where PyEval_CallObject* functions are called (see here). They aren't documented on Python's official document site, deprecated in 3.9, and removed in 3.13 (python/cpython#105107)

What was the purpose of these functions?

@clin1234
Copy link
Contributor

Also, replace _PyLong_NumBits (bc of python/cpython#108743)

@Avasam Avasam linked a pull request Jun 9, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants