I’m wondering if there’s any ongoing discussion or future plan to support PEP 779 – Standardizing the C-API for Static Python Interpreters in Python.NET.

https://peps.python.org/pep-0779/

Since PEP 779 introduces changes and standardization around the use of Python’s C-API for static and embedded interpreter scenarios, it may have implications for how Python.NET interfaces with the runtime, especially in embedded or ahead-of-time compilation environments.

Some points for consideration:

• Will Python.NET maintain compatibility with upcoming interpreter builds that implement PEP 779?
• Are there potential integration benefits or limitations we should be aware of?
• Could this impact hosting scenarios (e.g., .NET Core / NativeAOT + Python)?

I understand that PEP 779 is still in progress, but early evaluation might help ensure future compatibility and performance, especially thread safety issues.

Thanks for your work on this great project!