This plugin's syntax file treats None as a pythonBuiltinObj for Python 2, but as a pythonStatement for Python 3. This causes different highlighting for None in Python 2 versus Python 3, since pythonBuiltinObj maps to the Structure group, but pythonStatement maps to the Statement group.
- Why did this plugin's maintainers decide the highlighting group for
None should be different between Python 2 and Python 3? I'm not aware of anything different in the behavior of None from Python 2 to Python 3.
- Doesn't
None — a builtin constant — most logically map to the Constant group, rather than Structure or (especially) Statement? (The same goes for other builtin constants like True, False, etc.)
This plugin's syntax file treats
Noneas apythonBuiltinObjfor Python 2, but as apythonStatementfor Python 3. This causes different highlighting forNonein Python 2 versus Python 3, sincepythonBuiltinObjmaps to theStructuregroup, butpythonStatementmaps to theStatementgroup.Noneshould be different between Python 2 and Python 3? I'm not aware of anything different in the behavior ofNonefrom Python 2 to Python 3.None— a builtin constant — most logically map to theConstantgroup, rather thanStructureor (especially)Statement? (The same goes for other builtin constants likeTrue,False, etc.)