[issue30332] Errors that aren't actually defined are purple in the IDLE

Changes by Terry J. Reedy : -- type: -> behavior versions: +Python 3.6, Python 3.7 -Python 3.4, Python 3.5 ___ Python tracker ___ ___

[issue30332] Errors that aren't actually defined are purple in the IDLE

Terry J. Reedy added the comment: 3.4 only gets security fixes. There is no problem for me in 3.5.3. -- resolution: -> out of date stage: -> resolved status: open -> closed versions: -Python 3.6, Python 3.7 ___ Python tracker

[issue30332] Errors that aren't actually defined are purple in the IDLE

Jensen Taylor added the comment: I found this bug in python 3.4.1 and I believeit was a problem in 3.5.2 -- versions: +Python 3.4, Python 3.5 ___ Python tracker ___ _

[issue30332] Errors that aren't actually defined are purple in the IDLE

Terry J. Reedy added the comment: You neglected to say which version of Python you used. 2.7? 3.2? When I type the following in 3.5+ on Win10, >>> IOError, KeyError, PermissionError, int, list, FileNotFoundError all the names have the same builtins highlight. In 2.7 (and early 3.x), Permissio

[issue30332] Errors that aren't actually defined are purple in the IDLE

New submission from Jensen Taylor: Things like PermissionError and FileNotFoundError that come under IOError, or OSError in Python 3.7 -- assignee: -> terry.reedy components: +IDLE, Windows nosy: +paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware title: Errors that aren't act