…e checking, etc.) and have it parse either python 2 or 3.
Notes:
I've introduced variable py_ver, set to either 'PY27' or 'PY3'. We probably want to replace it with a dict {major: #, minor: #} or something like that.
I've had to wrap a bunch of code within function calls that introduce py_ver into existing files. It causes artificially many change lines according to Critique and may look a bit weird but it seems to be the simplest way to introduce this detail within the context of the testing framework.
I had to mutilate the check for Python > 3.5 to make it work for now but we'll correct it once we decide how to describe Python versions.
Fixed a few bugs in the code:
Case like 'globals a,b,c' where the first identifier appears again in the list.
Support for ur prefix for Python 2 string literals
…e checking, etc.) and have it parse either python 2 or 3.
Notes: