Cong Ma <m.c...@protonmail.ch> added the comment:
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.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue43615>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
