PyCharm 2017.1 WarmNeon coloring highlights builtin objects as keywords and makes highlighting 'odd'
已完成
In the WarmNeon highlighting color schema, in 2016.* we had the coloring for objects that are built ins such as "None", "False", "True", and other Python 2 Built In Constants showing up as Blue (as we would expect standard classes such as `str` or `TypeError` or `type(` functions to show up as.
However, this is no longer the case. How can I restore the 2016-style highlighting of such built in objects and classes?
请先登录再写评论。
Note that I've filed this as an actual issue on the bug tracker: https://youtrack.jetbrains.com/issue/PY-23364#tab=Comments
It looks to me like this is applying Python 3 highlighting as a 'default' instead of applying proper Python 2 handling for these built in constants. This is a major step backwards for Python 2, because they *cannot* be treated as Keyword highlights in Python 2 because they are not keywords.