You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All versions from C++11 upwards should be able to ingest the Python C headers IMHO.
C++98 may also apply, depending on how conservative you want to be.
Most of this is already in PEP-7. IMO we should move guidelines with user-visible effects out of the style guide.
This is not only about the external API, but the guideline PEP might be a good place for it.
Python requires C11 without optional features.
The public C API should be compatible with C++. (XXX Which C++?)
It is OK to use optional and compiler-specific features for optimizations and optional Python features.
We can update the C/C++ version or add an optional C feature can only be done with Steering Council approval. We recommend the SC check that:
(Note: atomics are an optional C feature, and AFAIK will be needed for nogil)
The text was updated successfully, but these errors were encountered: