# Python 3.x soon?

**URL:** <https://forum.inductiveautomation.com/t/python-3-x-soon/38635>\
**Category:** Ignition\
**Created:** [September 13, 2020, 5:24pm UTC](https://forum.inductiveautomation.com/t/python-3-x-soon/38635 "2020-09-13T17:24:09Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![Leor\_Fishman](https://avatars.discourse-cdn.com/v4/letter/l/e19adc/32.png) [@Leor\_Fishman](https://forum.inductiveautomation.com/u/Leor_Fishman)\
**Post date:** [May 21, 2025, 5:10pm UTC](https://forum.inductiveautomation.com/t/python-3-x-soon/38635/21 "2025-05-21T17:10:32Z")

</div>

My other question with a lot of people asking this is 'can your problem be solved by a separate python 3 script set and IPC between them'

---

<div class="post-metadata">

**Author:** ![diamond](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@diamond](https://forum.inductiveautomation.com/u/diamond)\
**Post date:** [May 21, 2025, 7:10pm UTC](https://forum.inductiveautomation.com/t/python-3-x-soon/38635/22 "2025-05-21T19:10:43Z")

</div>

One idea to support users who want to leverage Python 3.X for advanced charting or just for using specific C based libraries is to enhance the WebDev module to interface directly with a Python 3.X runtime—essentially acting like an API. This would allow users to execute Python scripts natively within Ignition’s Designer, eliminating the need for external API services...

---

<div class="post-metadata">

**Author:** ![Leor\_Fishman](https://avatars.discourse-cdn.com/v4/letter/l/e19adc/32.png) [@Leor\_Fishman](https://forum.inductiveautomation.com/u/Leor_Fishman)\
**Post date:** [May 21, 2025, 7:12pm UTC](https://forum.inductiveautomation.com/t/python-3-x-soon/38635/23 "2025-05-21T19:12:15Z")

</div>

i had a spec for setting this up that works about like....70% of the way, but you run into a lot of FFI issues

---

<div class="post-metadata">

**Author:** ![patrick.szalapski](https://avatars.discourse-cdn.com/v4/letter/p/ea666f/32.png) [@patrick.szalapski](https://forum.inductiveautomation.com/u/patrick.szalapski)\
**Post date:** [May 22, 2025, 1:31pm UTC](https://forum.inductiveautomation.com/t/python-3-x-soon/38635/24 "2025-05-22T13:31:49Z")

</div>

> > [@patrick.szalapski](#):
> >
> > With Jython clearly all but dead
> 
> Why do you say that? I get the emails from `jython-dev` and bug-fixing activity continues.

[Very few merges to master in the last year.](https://github.com/jython/jython/pulls?q=sort%3Aupdated-desc+is%3Apr+is%3Aclosed), and even fewer of them are substantive.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 22, 2025, 2:00pm UTC](https://forum.inductiveautomation.com/t/python-3-x-soon/38635/25 "2025-05-22T14:00:05Z")

</div>

Yeah, that's a good thing for stable, production-grade code.

Since jython exposes the entire JVM's resources, jython's _ **effective** _ functionality is that of the JVM it runs in.

---

<div class="post-metadata">

**Author:** ![patrick.szalapski](https://avatars.discourse-cdn.com/v4/letter/p/ea666f/32.png) [@patrick.szalapski](https://forum.inductiveautomation.com/u/patrick.szalapski)\
**Post date:** [May 22, 2025, 2:15pm UTC](https://forum.inductiveautomation.com/t/python-3-x-soon/38635/26 "2025-05-22T14:15:08Z")

</div>

Thank you for pointing out that thread...it didn't come up in my searches.

[Previous page](https://forum.inductiveautomation.com/t/python-3-x-soon/38635.md?page=1)