Modernizing Python Runtimes

I've been following the discussions about the new major version of pyRevit, particularly noting the efforts to migrate to .NET Standard or Core. I believe this may present an opportune moment to modernize the Python Runtimes.

I would love to find in PyRevit 5 a major upgrade to utilize a modern Python 3.12 runtime, enabling seamless interoperability with pip and opening pyRevit to a broader community of developers. This transition would empower developers to leverage the extensive Python ecosystem to create more powerful and communicative add-ins.

Currently, pyRevit ships with IronPython 2.7 and 3.4, both of which are old and unmaintained, while the IronPython project itself not progressing. The next major revision of pyRevit might be a good time to mark IronPython as deprecated and to use Cpython by default.

pyRevit includes CPython 3.8, which, while functional, is aging and will reach end-of-support in October 2024. This older version limits PyRevit's integration with the wider Python ecosystem through tools like pip, hindering its potential for expansion and collaboration. It appears that pyRevit relies on PythonNet to bind with the Common Language Runtime (CLR). While PythonNet is compatible with Python 3.12, the version currently integrated into PyRevit lags significantly behind the upstream, potentially due to compatibility issues. Addressing this discrepancy would be crucial in ensuring pyRevit's compatibility with modern Python runtimes. I understand from discussions on the pyRevit Discourse that there have been challenges with CPython support, with plans to rectify them in the next major version. I wish to help resolving these issues and would appreciate insights into the current status and roadmap for improving CPython integration.

In summary, I hope the time has come to mark as deprecated outdated Python runtimes, embrace modern Python 3.12, and enhance interoperability with the wider Python ecosystem. This initiative would mark a significant milestone in pyRevit's evolution, making it more robust, accessible, and future-proof.

Looking forward to discussing and collaborating on this exciting endeavor.

Review the existing IronPython and CPython runtime integration and the PythonNet version used by pyRevit; the issue provides no file or test entry point. Clarify the target runtime, compatibility constraints, and deprecation scope with maintainers. Done would require an agreed migration plan and validation of Python 3.12 interoperability.