This post is a heads up for changes coming in the next versions of FinalBuilder and Automise.
TLDR; - stop using Iron Python in FinalBuilder and Automise.
We have been encouraging users to not use the Iron Python itegration for some time now, due to memory leaks that we were not able to control. The project has languished over the years since Microsoft pulled support.
In the next major versions we will remove Iron Python completely
We did spend quite some time investigating integration Python support, but hit roadblocks due to threading issues with Python.
We are working on replacing the JScript and VBScript engines. Those tasks have consumed considerable resources over the last few years (before ai was really a thing) - we are making good progress with that now and the new scripting engine integration is being worked on at the moment. We are hoping for 100% compatibility with the existing Active Scripting based JScript and VBScript engines. For the Javascript engine, we have the ecma tc39/262 test suite, with our new engine passing 400 short of the full 52K tests - the remaining failures are for things that are not relevant to FB/AT.
The new VBScript engine shares the same virtual machine/bytecode interpreter as the Javascript engine, however no standard test suite exists, so we are less confident about it. We have been using the test suite that the Wine project used when they implemented active scripting - those all pass, along with thousands of unit tests.