Managing Iron/Cpython transition

@jacob.small
You say migrate to CPython - but it’s known that there are issues with CPython and Revit API (pretty major ones in my opinion).

It’s going to be difficult to migrate completely until CPython plays nice with the major platform that most users are using Dynamo for.

Also - you say IronPython is a security risk. Can you explain more about where that risk might be (for us non-IT folks)? Is it a risk just using downloaded external packages using IronPython (but no risk if you are developing for your own use - so Package Authors should migrate but its totally safe for one to use internally to one’s own company)? Or is the risk literally just in the mere presence of IronPython on your machine (so really the better solution would be to get all versions in use with Revit 2019 and newer using CPython and cleanse IronPython entirely)?