# Python debugger desperately needed!

**URL:** <https://forum.inductiveautomation.com/t/python-debugger-desperately-needed/85942>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [February 19, 2024, 3:29pm UTC](https://forum.inductiveautomation.com/t/python-debugger-desperately-needed/85942 "2024-02-19T15:29:52Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![pgmo](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@pgmo](https://forum.inductiveautomation.com/u/pgmo)\
**Post date:** [February 19, 2024, 3:29pm UTC](https://forum.inductiveautomation.com/t/python-debugger-desperately-needed/85942/1 "2024-02-19T15:29:52Z")

</div>

Hi all,  
this post just to know if there's any plan in the near future to get an Ignition platform with a **Python debugger**.  
Consider next scenario: you are 5 developers on the same gateway, each implementing his own Python highly complicated logic and each `print`ing debug messages to the gateway plus `exceptions` prints out. Question: how can you imagine to get the job done in a reasonably short time if you must go through 100s of log `print`s to find your own mistakes?  
Sorry for my complain, but I'm really getting desperate and frustrated!

Now back to my starting question: when the debugger? I know it's not that easy, but a framework like Ignition, that you can really do anything you want with, needs urgently a debugger to be 100% enjoyable!

Thanks, regards

---

<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:** [February 19, 2024, 3:46pm UTC](https://forum.inductiveautomation.com/t/python-debugger-desperately-needed/85942/2 "2024-02-19T15:46:22Z")

</div>

I don't expect it will ever happen. It is difficult enough to use a java debugger, much less any kind of nested debugger.

But, this is the real problem:

> [@pgmo](#):
>
> you are 5 developers on the same gateway

Develop on isolated gateways--each developer on their own. Designers on a production gateway should be **deploying** well-tested projects, not developing new ones.

---

<div class="post-metadata">

**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\
**Post date:** [February 19, 2024, 3:46pm UTC](https://forum.inductiveautomation.com/t/python-debugger-desperately-needed/85942/3 "2024-02-19T15:46:58Z")

</div>

If you're using the same logger name on the same gateway then yes this will be difficult, but if you use different logger names then you can filter by that in the gateway logs. That's the first easy suggestion I would suggest if you don't want to change anything else about your workflow.

---

<div class="post-metadata">

**Author:** ![pgmo](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@pgmo](https://forum.inductiveautomation.com/u/pgmo)\
**Post date:** [February 19, 2024, 4:03pm UTC](https://forum.inductiveautomation.com/t/python-debugger-desperately-needed/85942/4 "2024-02-19T16:03:16Z")

</div>

Your suggestions are appreciated, but think your same suggestions goes to someone that is developing a non trivial .NET application with MS Visual Studio? I cannot really imagine the answer! And I think that Ignition development is really as powerful as .NET development, even more, I would say ... but for debugging!

---

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [February 19, 2024, 4:11pm UTC](https://forum.inductiveautomation.com/t/python-debugger-desperately-needed/85942/5 "2024-02-19T16:11:37Z")

</div>

> [@pgmo](#):
>
> that is developing a non trivial .NET application with MS Visual Studio?

Not really. Python is an interpreted language. .NET languages, as far as I am aware, are all compiled languages, so not really a 1-1.

Add to that, that the scripting language in Ignition is running on the JVM, you've just added a whole other layer of complication. Jython can, and should tie into the Java layer, and so a debugger would be expected to be able to step into java functions, and in order to do that you would need a decompiler to go from Byte Code back to Java Class. It's just not a simple thing.

---

<div class="post-metadata">

**Author:** ![pgmo](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@pgmo](https://forum.inductiveautomation.com/u/pgmo)\
**Post date:** [February 19, 2024, 4:16pm UTC](https://forum.inductiveautomation.com/t/python-debugger-desperately-needed/85942/6 "2024-02-19T16:16:52Z")

</div>

> [@lrose](#):
>
> It's just not a simple thing

I know it's really complicated, but such a wonderful platform as Ignition does need it, to be 100% fit for all purposes!

> [@lrose](#):
>
> Not really. Python is an interpreted language. .NET languages, as far as I am aware, are all compiled languages, so not really a 1-1.

I'm not comparing the two platforms as far as the technology is concerned, but as far as the power and therefore intended audience: Ignition platform could by a choice wherever .NET is, in my opinion, with the added advantage that you can communicate with the shop floor with ease.

---

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [February 19, 2024, 4:45pm UTC](https://forum.inductiveautomation.com/t/python-debugger-desperately-needed/85942/7 "2024-02-19T16:45:27Z")

</div>

> [@pgmo](#):
>
> Ignition platform could by a choice wherever .NET is

From and Industrial SCADA perspective, absolutely. But, that's not really the domain of those languages, just like JAVA.

You want to treat Ignition like an IDE, but that isn't what it is.

Don't get me wrong, if IA were to come along and introduce a debugger, I would be among the first to adopt it's use and claim it's awesomeness. I just don't see it happening. There are too many other things that have a way higher priority to most users, myself included.

---

<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:** [February 19, 2024, 5:04pm UTC](https://forum.inductiveautomation.com/t/python-debugger-desperately-needed/85942/8 "2024-02-19T17:04:27Z")

</div>

> [@pgmo](#):
>
> such a wonderful platform as Ignition

Yes, it is wonderful. No, your request almost certainly cannot be satisfied, and certainly not within some years. Make a feature request.

But in the meantime, learn to debug jython in Ignition without a debugger. It is your only choice for the foreseeable future.
