Run mypy parser against a lot of Python code and file bugs for errors

[JukkaL]

The mypy parser still doesn't support all of Python 3 syntax. Run the parser against a corpus of Python code and file tasks for any remaining parser issues. Note that there are open 2 pull requests that implement some new syntax (#367 and #483).

[JukkaL]

Some issues I've found:

• namedtuple(...) as base class EDIT: fixed
• nonlocal EDIT: fixed
• *foo lvalues (already fixed in Checking of starred expressions #483)
• some nested tuple lvalues in for loops (profile.py in Python 3.2 stdlib, line 546) EDIT: false alarm?

TODO: File the above as issues, or point to existing issues.

[spkersten]

I'll investigate the nested tuple lvalues issue. Apparently I overlooked something.

[JukkaL]

Added open issue #494 for nonlocal support.

EDIT: implemented (thanks @spkersten!)

[JukkaL]

There already is the issue #460 for namedtuple.

EDIT: implemented

[JukkaL]

Also #60, relative imports.

EDIT: implemented (thanks @mason-bially!)

[spkersten]

I'm having trouble reproducing the issue with nested tuple lvalues. When I try running mypy on profile.py, it complains it cannot find all kind of modules.

[JukkaL]

profile.py now works for me as well. Odd. I'll try rerunning the whole thing and see if I misreported the issue.

[JukkaL]

Complex literals was another missing missing feature (just pushed an implementation by @spkersten, thanks!).

[JukkaL]

Another missing feature is yield expressions: #498

[JukkaL]

Mypy doesn't support the ... expression: #524

EDIT: implemented by @spkersten

[JukkaL]

Calls such as f(x=y, *z) where we have *args and a keyword arg aren't accepted (#153).

Example in the wild: Python-3.2.3, Lib/pickle.py, line 344.

EDIT: fixed

[JukkaL]

Escapes within raw string literals are broken: #532

EDIT: fixed