ScriptEditor why Try Catch is not default option?

[Petras_Vestartas]

The debugging of Python in Grasshopper Script editor often does not show exact line of error.

I most often need to wrap my code around try statement:

        try:
             ...
        except Exception as e:
            import traceback
            traceback.print_exc()

I am wondering why this is not default case?
For instance I get an error, it names or does not, and does not tell exact line. It feels there is some sort of try catch statement in ScriptEditor but it is not fully printed for a user…

[eirannejad (Ehsan Iran-Nejad)]

@Petras_Vestartas The editor should throw the error and mark the line in the editor control. If this is not the case there is a bug. Would you mind sending me an example script that repeats the issue?

[Petras_Vestartas]

@eirannejad This is the example. On purpose I try to get object by index, which is way too high. The simpler error pop out, but it does not say where. This kind of error is very hard to debug on larger code.
7_assign_directions_and_joint_types.gh (51.6 KB)

Also curious if on your machine the pypi dependencies both Mac and Windows install properly.

[eirannejad (Ehsan Iran-Nejad)]

I ran this on both windows and macOS and this is what I am seeing:

What am I missing?

(wood_nano fails to install on my arm64 mac. I see that it only supports x86_64 at the moment)

[Petras_Vestartas]

Nothing.

Strange, on my pc there is no line number. I have latest service release. Thank you for checking it.

[Alain (Alain Cormier)]

I tested this as well, in dark mode in case it had anything to do with it but I have the same result as Ehsan.

[eirannejad (Ehsan Iran-Nejad)]

@Petras_Vestartas It might have already been fixed in our builds then Good news!