None is highlighted differently in Python 3 than in Python 2 #33
Description
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
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. - Doesn't
None— a builtin constant — most logically map to theConstantgroup, rather thanStructureor (especially)Statement? (The same goes for other builtin constants likeTrue,False, etc.)
Activity
hdima commentedon Oct 31, 2015
The idea is to show differences in implementation of
None. In Python 2Noneis a built-in object/type and it was possible to assign toNoneprior to Python 2.4. In Python 3Noneis a part of the grammar so it can be seen more as a statement. And the same goes forTrueandFalse.nfnty commentedon Mar 3, 2017
This has been fixed over at the fork vim-python/python-syntax.