Recently, a issue about C++20 compatibility was reported: "The Python library will not compile with a C++2020 compiler because the code uses the reserved “module” keyword" https://github.com/python/cpython/issues/83536 In fact, after a long study, Python C API is *not* affected by this issue. Using "module" remains valid in C++20: see the issue for details. Victor On Thu, Apr 28, 2022 at 5:19 PM Antoine Pitrou <antoine@python.org> wrote:
On Thu, 28 Apr 2022 22:03:25 +0900 "Stephen J. Turnbull" <stephenjturnbull@gmail.com> wrote:
h.vetinari@gmx.com writes:
While I don't know who proposed C++11 or where, I'd therefore like to propose to move to _at least_ C++14.
What benefits does this have for Python development?
Let me second that question as well.
I work on Apache Arrow, where the C++ parts require C++11 (and we can't go further than this for now because of R compatibility concerns). We could say that enabling the Python bindings switches the required C++ version to C++14, but that would bring complication for no actual again given that you're not likely to benefit from C++14 features in the header files of a *C* project, are you?
Regards
Antoine.
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/BIK3SEBQ... Code of Conduct: http://python.org/psf/codeofconduct/
-- Night gathers, and now my watch begins. It shall not end until my death.