@eirannejad Please see the below screenshot. The error is given without a line number. Thus it is hard to debug. Unfortunately I cannot share the file. External script file is a must (vim motions user). Is this a known bug? Thanks!
Just FYI, I edited the topic. GhPython is the name of the old IronPython editor. Your screenshot is the new Rhino 8 Python 3 editor.
@AndersDeleuran Thanks, what tag is to be used for Py3? Edit: Got it, GhPython > ghpython.
@eirannejad Upon further investigation, this problem only exists with specific errors that do not show the line number at the end of the error message (the missing parentheses error is one of them). In contrast to that, import errors show the line number at the end of the message.
I don’t know if there are specific categories tags, but I usually post under Grasshopper Developer
with tags that relate to the relevant components/languages. See e.g:
But whatever works
@silvano Yes. There are a subset of errors (I don’t have a list of all of them) that do not show the error line currently. This is either a technical limitation in figuring out the line number in Pythonnet, or might be a parser issue that tries to grab line number from python exception messages.
Either way it would be great if you can share an example that I can use to repeat and fix the issue.
@eirannejad Please find example of the issue below. Thanks for looking into it.
LinenumberBug.gh (5.2 KB)
LinenumberBug.py (54 Bytes)
Thank you!
RH-86122 Python component does not include error line
RH-86122 is fixed in Rhino 8 Service Release 18 Release Candidate