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
Can you reproduce the bug with PYTHONASYNCIODEBUG in env?: n/a
Does uvloop behave differently from vanilla asyncio? How?: n/a
I try to build uvloop for Fedora Linux 41 with Python 3.13.0a5.
The build fails with the information below.
uvloop/loop.c: In function ‘__pyx_f_6uvloop_4loop_9UVProcess__after_fork’:
uvloop/loop.c:129617:5: error: implicit declaration of function ‘_Py_RestoreSignals’ [-Werror=implicit-function-declaration]
129617 | _Py_RestoreSignals();
| ^~~~~~~~~~~~~~~~~~
The text was updated successfully, but these errors were encountered:
This one is a warning here on a pyenv-installed 3.13.0b1 (not sure if -Werror=implicit-function-declaration in the original report comes from Fedora defaults or what), but there are multiple actual errors:
uvloop/loop.c:4446:105: error: invalid type argument of ‘->’ (have ‘int’)
4446 | __pyx_assertions_enabled_flag = ! _PyInterpreterState_GetConfig(__Pyx_PyThreadState_Current->interp)->optimization_level;
| ^~
[...]
uvloop/loop.c: In function ‘__Pyx_PyInt_As_int’:
uvloop/loop.c:177390:27: error: too few arguments to function ‘_PyLong_AsByteArray’
177390 | int ret = _PyLong_AsByteArray((PyLongObject *)v,
| ^~~~~~~~~~~~~~~~~~~
[...]
PYTHONASYNCIODEBUG
in env?: n/aI try to build uvloop for Fedora Linux 41 with Python 3.13.0a5.
The build fails with the information below.
The text was updated successfully, but these errors were encountered: