Skip to main content
Archived

Python debugging

Related products:FME Form
jeand
Contributor

Hi,

I think that would be great if we could export the Python code from FME into a temporary working folder to let us debugging with our prefered application. (Ex: PyCharm, Eclipse, etc...)


Exemple of what we could find into a PythonCaller, it's 2 new buttons:

  • Export code for debugging
  • Re-import code

When we click export code, the Startup/Shutdown Python code needs to be exported to and a import line should be added on the script we want to debug in case we refer classes of functions from them.


When we run the process, FME should use the external exported script instead of embeded code. In this way, we would be able to debug with our favorite software.


Once the debug is done and perhaps the external code is modified, we should be able to re-import this code into FME.


This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

mattwilkie
Supporter
Forum|alt.badge.img+11

I agree with the general intent but am not so sure on the particular suggestion. Rather than 2 buttons, just have one: [Edit externally].

Pushing the button launches either a) what the OS has defined as the default edit handler for `.py`, or b) an FME preference for Path to tool to edit .py files.

FME watches the file handle. When file handle changes, e.g. the application modifies it or closes it. It automatically imports the new contents.

FME doesn't need to concern itself with a "import the changes?" prompt or UI button. It's up the user to not modify (save) the file if they don't want to keep the experiment. (It would be okay, great even, if FME's edit widget saved the before and after state so that Undo works.)

 

jeand
Contributor
Forum|alt.badge.img+5
  • jeandContributor
  • Contributor
  • February 8, 2023

Hi @mattw1ilkie​, this is more a starting idea. For Safe to implement a better IDE Python Editor and perhaps with a debugger it could cost a lot. The main idea it's to let FME edit our code into an another IDE and be able to debug it.

mattwilkie
Supporter
Forum|alt.badge.img+11

Oh yes, exactly! I didn't mean to sound like I was suggesting Safe build an IDE. My suggestion is about making using any external IDE of choice faster and smoother, less clicks.

LizAtSafe
Safer
Forum|alt.badge.img+15
Updated idea statusGathering Interest→Archived
Idea merged into:
All the votes from this idea have been transferred.

Helpful Members This Week

Community Stats

31,031
Posts
117,608
Replies
38,810
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.