Remove distracted red bar from IDLE for some SyntaxErrors

Offen

#93,966 erstellt am 17.6.2022 3 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@terryjreedy arbeitet bereits daran.

Seit 17.6.2022.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

topic-IDLE type-bug

Bug report

This may be more an distracting cosmetic issue than a true bug, but it is something that can be fixed easily.

As Raymond Hettinger mentioned a while ago on Twitter (https://twitter.com/raymondh/status/1501700903870468099), when a SyntaxError is raised and the location corresponds to the "\n" at the end of a line, a huge red highlighted region is shown at the end of the invalid line.

For example, type

from math

followed by enter. This red highlighted line will remain on the screen until another SyntaxError occurs.
Unlike cases where a SyntaxError highlights just a few characters pointing at a specific problem, this adds really no informative value, once the user starts entering some new code.

Your environment

I have reproduced this will IDLE on Windows 10 on all Python versions I have installed, from 3.6 to 3.11 inclusively.

Proposed fix

I have been able to fix this on a custom version of IDLE (friendly_idle) by doing the following:

In pyshell.ModifiedInterpreter.transfer_path which sets up some values at the beginning of a new process,
define the following:

self.error_at_end_of_line = False

In pyshell.ModifiedInterpreter.showsyntaxerror, add the last line shown below:

        if lineno == 1:
            pos = "iomark + %d chars" % (offset - 1)
        else:
            pos = "iomark linestart + %d lines + %d chars" % (lineno - 1, offset - 1)
        self.error_at_end_of_line = text.get(pos) == "\n"  # <-- add this

At the beginning of pyshell.ModifiedInterpreter.runsource, add the following:

        if self.error_at_end_of_line:
            self.error_at_end_of_line = False
            self.tkconsole.text.tag_remove("ERROR", "1.0", "end")

If desired, I could do a pull request that would include these changes.

Linked PRs

gh-157595

Vorherrschende Sprache: Python
Sterne: 77.2k
Forks: 36k
Ø Merge: 1 T. 9 Std.
Gemergte PRs (30 T.): 558

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus python/cpython

docs: Zipfile contains a 13-years outdated warning regarding path sanitization Offen

docs pending

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100

python/cpython#157339 · 10 Kommentare · Erstellt am 11.9.2026
pydoc HTML output is not responsive and has no viewport meta in released versions Offen

stdlib type-feature

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100

python/cpython#155601 · 2 Kommentare · Erstellt am 12.8.2026
`zipfile.ZipFile.writestr()` raises `AttributeError` instead of accepting `os.PathLike` objects (e.g. `pathlib.Path`) Offen

stdlib type-feature

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100

python/cpython#153771 · 5 Kommentare · Erstellt am 15.7.2026
BOLT-WARNING: specifying numeric value "1" for option -icf is deprecated Offen

build type-bug

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100

python/cpython#149708 · 1 Kommentar · Erstellt am 12.5.2026
Expose message ID list from `ReferencesHeader` Offen

stdlib topic-email type-feature

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100

python/cpython#148797 · 3 Kommentare · Erstellt am 20.4.2026

Alle Issues in python/cpython