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
Describe the bug
A clear and concise description of what the bug is.
In generated c code, the generated macro __Pyx_PyFrame_SetLineNumber still uses fields of PyFrameObject, but PyFrameObject has moved to internal API.
I was fixing the reported bug https://bugzilla.redhat.com/show_bug.cgi?id=2062338
but it appears that the problem comes from the generated code by cython.
python 3.10 and cython works fine on this code.
After removing some warnings, I still obtain this error with the last docker image of python : 3.11-rc-bullseye
wget https://www.imcce.fr/content/medias/recherche/equipes/asd/calceph/calceph-3.5.1.tar.gz
tar xzf calceph-3.5.1.tar.gz
cd calceph-3.5.1
cd pythonapi/src
cython -3 calcephpy.pyx
cd ../..
./configure --enable-python=yes --enable-fortran=no && make
Expected behavior
A clear and concise description of what you expected to happen.
Environment (please complete the following information):
OS: Linux
Python version 3.11.0a6
Cython version 0.29.28
Additional context
Add any other context about the problem here.
Describe the bug
A clear and concise description of what the bug is.
In generated c code, the generated macro __Pyx_PyFrame_SetLineNumber still uses fields of PyFrameObject, but PyFrameObject has moved to internal API.
I was fixing the reported bug https://bugzilla.redhat.com/show_bug.cgi?id=2062338
but it appears that the problem comes from the generated code by cython.
python 3.10 and cython works fine on this code.
After removing some warnings, I still obtain this error with the last docker image of python : 3.11-rc-bullseye
To Reproduce
Code to reproduce the behaviour:
Expected behavior
A clear and concise description of what you expected to happen.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
Another project has maybe the same issue :
https://www.mail-archive.com/[email protected]/msg1906195.html
The text was updated successfully, but these errors were encountered: