mention nogil and jit

peps/pep-0733.rst

@@ -63,12 +63,14 @@ Python into C/C++ applications and to write extension modules in C/C++.
 These capabilities were instrumental to the growth of Python's ecosystem.
 Over the decades, the C API grew to provide different tiers of stability,
 conventions changed, and new usage patterns have emerged, such as bindings
-to languages other than C/C++. However, this growth was not supported by
-clearly documented guidelines, resulting in inconsitent approaches to
-API design in different subsystems of CPython. In addition, CPython is
-no longer the only implementation of Python, and some of the design
-decisions made when it was, are difficult for alternative implementations
-to work with
+to languages other than C/C++. In the next few years, new developments
+are expected to further test the C API, such as the removal of the GIL
+and the development of a JIT compiler. However, this growth was not
+supported by clearly documented guidelines, resulting in inconsitent
+approaches to API design in different subsystems of CPython. In addition,
+CPython is no longer the only implementation of Python, and some of the
+design decisions made when it was, are difficult for alternative
+implementations to work with
 [`Issue 64 <https://github.com/capi-workgroup/problems/issues/64>`__].
 In the meantime, lessons were learned and mistakes in both the design
 and the implementation of the C API were identified.