Theyre going to have to face it sooner or later, as i know many firms are beginning to reject ironpython2 due to vulnerability concerns (mine included).
Cpython3 has quite a few challenges to my understanding in pyrevit and the general stance is to avoid it in many cases, and the core tools are built in ironpython2.7 still.
Like dynamo, they will probably have to jump to pythonnet or a newer ironpython to remain a heavily used app by larger firms, but it would likely be a lot of work.
I love pyrevit for what it is, but having jumped to c# can comfortably say this should be the endgame for any firm/person looking to deploy stable, secure and scalable solutions (+ web integrations from there). Its not for everyone, and has a steeper learnint curve with a higher ceiling of opportunity.
We pushed it hard where i work initially, and had much success, but redeveloping all our tools in c# has given us an edge over what we had before in pyrevit (we have 200+ custom tools/buttons built/rebuilt in both).
Pyrevit is ultimately a dependency with no guarantee of maintenance, but for now a passionate community doing great things with/for it.
For any pyrevit users curious about c#, i have an open sourced toolbar here that is heavily inspired by pyrevit, with similar forms and toolbar structure:
In relation to this topic, my toolbar integrates the closedxml package to import/export excel which is compatible with all revit versions so far up to 2026. I abstract it into a set of functions in this library: