You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I have discovered that the declarations of PPyDescrObject and its descendants are not aligned with the current state of descrobject.h in Python 3.3+. The structure was extended in commit python/cpython@9d57481 . A patch is attached. I am also attaching a tiny patch to add PyGetSetDescr_Type declaration.
I have applied your patches. These structures are not used anywhere in the P4D code, so the discrepancy had no impact. I would be interested to know whether and how you are using them.
This help document explains how to use them from python code, but I am not sure how it relates to the C-API.
Thank you very much for applying the patches. The PPyDescrObject declarations are of limited use. I am trying to use them from C-API to enum class elements. PyObject_GetAttr() invoked for a class do return these instances and for a GetSet property it is a PPyGetSetDescrObject instance.
Hello,
I have discovered that the declarations of PPyDescrObject and its descendants are not aligned with the current state of descrobject.h in Python 3.3+. The structure was extended in commit python/cpython@9d57481 . A patch is attached. I am also attaching a tiny patch to add PyGetSetDescr_Type declaration.
Best regards,
Joe
0001-reflect-PyDescr_COMMON-change-made-to-Python-3.3.patch
0001-add-PyGetSetDescr_Type.patch
The text was updated successfully, but these errors were encountered: