Line no longer highlighted on error when executing scripts from text editor #120859

New Issue

Dmitry C. · 2024-04-20T19:56:23+02:00

Dmitry C. commented

2024-04-20 19:56:23 +02:00

System: Windows 10
Broken: Blender 4.1.0, 4.2.0-alpha-main-026f8e8bdf68
Worked: Blender 4.0.2

Open blender, switch to text editor, create new text, type:

pass
blah
pass

Execute with the play button.

In previous versions, the cursor would move to the end of the second line.
Starting from 4.1.0 it always ends up at the bottom.

System: Windows 10 Broken: Blender 4.1.0, 4.2.0-alpha-main-026f8e8bdf68 Worked: Blender 4.0.2 Open blender, switch to text editor, create new text, type: ``` pass blah pass ``` Execute with the play button. In previous versions, the cursor would move to the end of the second line. Starting from 4.1.0 it always ends up at the bottom.

Dmitry C. added the

labels 2024-04-20 19:56:24 +02:00

YimingWu commented

2024-04-22 04:31:46 +02:00

Caused by 9903a692cc cc @ideasman42

This change made text editor to only jump to lines when the python exception is "Syntax Error" instead all errors that can be pointed to a line.

Consider this as a high priority since it's broken recently.

Caused by 9903a692cc97581f324128ac1cb4cf3 cc @ideasman42 This change made text editor to only jump to lines when the python exception is "Syntax Error" instead all errors that can be pointed to a line. Consider this as a high priority since it's broken recently.

YimingWu added

and removed

labels 2024-04-22 04:32:21 +02:00

Campbell Barton commented

2024-04-23 06:54:45 +02:00

This is a regression caused when moving from Python 3.10 to 3.11 (tested 172a6d65a60c8647b49763568e1c76e2b00e970c with both versions of Python and the issue only happens with Python 3.11).

This is a regression caused when moving from Python 3.10 to 3.11 (tested `172a6d65a60c8647b49763568e1c76e2b00e970c` with both versions of Python and the issue only happens with Python 3.11).

YimingWu commented

2024-04-23 09:46:19 +02:00

Then I guess newer version of python didn't report the same exception as Syntax Error. I'll take a look at how to fix this.