# GraalPy or GraalJS with Ignition **URL:** \ **Category:** Ignition\ **Tags:** python\ **Created:** [September 18, 2024, 3:34pm UTC](https://forum.inductiveautomation.com/t/graalpy-or-graaljs-with-ignition/96136 "2024-09-18T15:34:25Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [September 18, 2024, 10:01pm UTC](https://forum.inductiveautomation.com/t/graalpy-or-graaljs-with-ignition/96136/3 "2024-09-18T22:01:25Z")
> [@Nick\_Hotto](#): > > GraalPy gaining traction Citation needed 😄 GraalVM is very interesting, but one big worry about integrating an Oracle product into Ignition is long-term licensing. If GraalVM suddenly becomes a commercial project, but is deeply entangled into our system, we're "on the hook" to pay for it, with few other options. Suffice to say that we're not pretending Jython is the forever solution for Ignition scripting - but we're also not convinced by any of the alternative solutions we've encountered yet. > [@Python version 3 update?](https://forum.inductiveautomation.com/t/python-version-3-update/10106/9): > > I guess I can paraphrase what I said on stage at the dev panel at this year's ICC, for posterity and so I can link to this in the future: So, the question people usually ask is "When is Python 3 coming to Ignition?". But in practice, there's really two broad reasons people are actually asking that question: They've heard that Python 2.7 is deprecated/old/unmaintained/a security risk/whatever. But that doesn't apply to Ignition, for a few reasons: When folks say "Python" out in the world, the… --- _[View the full topic](https://forum.inductiveautomation.com/t/graalpy-or-graaljs-with-ignition/96136)._