Message389457
Hello Victor,
I think you're right. This is bogus on my part. TL;DR: The Python version is 3.8 but I was trying to understand what's going on using the latest source.
Full version: I was trying to understand why the following C file when compiled with -shared using Clang 11 generates a call to Py_FatalError():
```
#define PY_SSIZE_T_CLEAN
#include "Python.h"
void
unreach(void)
{
Py_UNREACHABLE();
}
```
The headers Python.h and also the ones pulled in by it were actually from Python 3.8 release, which unconditionally defines the macro as a call to Py_FatalError. |
|
Date |
User |
Action |
Args |
2021-03-24 14:30:35 | congma | set | recipients:
+ congma, vstinner |
2021-03-24 14:30:35 | congma | set | messageid: <1616596235.03.0.527117793182.issue43615@roundup.psfhosted.org> |
2021-03-24 14:30:35 | congma | link | issue43615 messages |
2021-03-24 14:30:34 | congma | create | |
|