Exactly one of my ideas too. Its very not productive to delete or comment scripts before launching the workspace.

Extent the idea to pre-SQL, post-SQL and TCL startup/shutdown...

Extent the Startup and the Shutdown scrypt in the main tab, the script will have a better visibility in the workbench for the user.

'

and delete the Output for each transformer !

This came up on a desktop basic course yesterday so I vote for this

Any momentum on this? @daleatsafe

This really needs to be implemented. Particularly since feature caching has been introduced. If I run my script to a particular transformer, it runs my python startup and shutdown script. If I then run to the next transformer (using cached features) it runs my startup and shutdown scripts again. Some of these scripts are not trivial, the startup script deletes a geometric network, the shutdown script turns off versioning on the datasets, rebuilds the geometric network and turns versioning back on again. This doesn't need to occur every time I want to follow the outputs of each transformer. Please enable a switch to ignore startup/shutdown scripts when running a translation.

Can you just create a start.txt and/or stop.txt file and populate it with "Debug" when you want to do testing and set it to something else otherwise? Then at the top of you python you could do:

import fme, fmeobjects

f = open("start.txt", "r")

if (f.readline() == "Debug"):

  print("***** in Debug Mode, skipping normal startup *****")

else:  

  print("****** Running usual startup *****")

# USUAL STARTUP ROUTINE HERE

Is there a reason that this isn't a feature yet? It really would save a lot of time

Yes please , +1!

Any update on this when it might become a feature?

One workaround in Python is to put triple double-quotes at the top ("""). This effectively converts the entire script into just a string, which Python does nothing with.

(PS: It doesn't really work if you use triple double-quotes within your script)