ctypes should have an option to *not* catch c++ exceptions

Feature or enhancement

Proposal:

The ctypes module catches native exceptions and turns them into Python exceptions. In 99.99% of the cases this is exactly what you want, as a Python developer.

But the exception (pun unintended) is when the native exception is repeatable, but only happens in situations where you have no control.

An example is native exceptions that only occur when running your Python code which depends on numerous native libraries on the GitHub Windows runner. I have just had this happen to me for the third time in a couple of years. In the previous two cases the problem was some Python package (or native package it depends on) having a private copy of an outdated MSVC runtime library (or depending on some outdated copy). This is impossible to trace, because it is not repeatable on a development machine, and it isn't even repeatable when capturing the built folder and running the tests on you development machine.

Some mechanism (either a global method in ctypes to disable the exception-catching, or an environment variable PYTHON_CTYPES_DONT_CATCH_EXCEPTIONS) would help immensely, because I could use a debugging Python and a stack trace to pinpoint where the exception happens.

Has this already been discussed elsewhere?

This is a minor feature, which does not need previous discussion elsewhere

Links to previous discussion of this feature:

No response

该 payload 提到了 ctypes 模块，但没有指出源文件或测试。首先定位 ctypes 的原生异常捕获路径，并检查当前的 Python 异常转换是如何测试的。将全局开关与 PYTHON_CTYPES_DONT_CATCH_EXCEPTIONS 进行比较，并将“已完成”定义为：提供一种有文档说明且经过测试的方式，在不改变默认行为的情况下为调试保留原生异常。