| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| async-Use-correct-T_BOOL-type-for-_asyncio_future_blockin.patch | async: Use correct T_BOOL type for _asyncio_future_blocking Declaring a PyMemberDef with type T_BOOL requires the corresponding C type to be char, with value 0 or 1: when the member is read, CPython will effectively be dereferencing `* (char *) &pygiasync._asyncio_future_blocking`. On little-endian architectures, in practice this worked, because the low-order bits of an int are in the first byte, which would take value 0 or 1 as desired, with all other bits zero. However, on big-endian architectures, the low-order bits of an int are in the last byte, so reading the _asyncio_future_blocking attribute from Python code would in practice always produce 0, even when the int field had been set to 1 from C code. |
Simon McVittie <smcv@debian.org> | yes | debian upstream | 2024-10-23 |