[issue13629] _PyParser_TokenNames does not match up with the token.h numbers

Changes by Meador Inge : -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___

[issue13629] _PyParser_TokenNames does not match up with the token.h numbers

Roundup Robot added the comment: New changeset 1c0c6fa7341c by Meador Inge in branch '3.2': Issue #13629: Renumber the tokens in token.h to match the _PyParser_TokenNames indexes. http://hg.python.org/cpython/rev/1c0c6fa7341c New changeset c0660d7cc1fe by Meador Inge in branch 'default': Issue

[issue13629] _PyParser_TokenNames does not match up with the token.h numbers

Meador Inge added the comment: Here is a patch that renumber the tokens. I also regenerated token.py. -- nosy: +georg.brandl Added file: http://bugs.python.org/file24225/renumber-tokens.patch ___ Python tracker _

[issue13629] _PyParser_TokenNames does not match up with the token.h numbers

Meador Inge added the comment: > Is there a reason not to renumber token.h? I thought about that, but at the time I wasn't sure whether or not that would break anything. I went with the current patch because it is lower risk. On the other hand, proper clients of token.h should only be using t

[issue13629] _PyParser_TokenNames does not match up with the token.h numbers

Martin v. Löwis added the comment: Is there a reason not to renumber token.h? -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs

[issue13629] _PyParser_TokenNames does not match up with the token.h numbers

New submission from Meador Inge : When making the changes to remove backticks in eb2f70fdbf32, the _PyParser_TokenNames table was incorrectly updated. Now the indexes into _PyParser_TokenNames don't match the token numbers. This can be seen in the output of 'python -d': $ echo '2 << 1' |