1
0
forked from VimPlug/jedi
Commit Graph

13 Commits

Author SHA1 Message Date
Dave Halter
a373e34229 The parser without error recovery raises an error now if he's not able to parse something. 2015-12-25 18:53:05 +01:00
Dave Halter
936cef97e9 Fix param position lookups. Also forward annotations have the correct resolution path now (starting at the end of the file). 2015-12-22 11:25:32 +01:00
Dave Halter
5791860861 Actual forward reference annotations are working pretty smooth now. 2015-12-20 22:57:41 +01:00
Dave Halter
c4906e0e3f Rework the parser so we can use arbitrary start nodes of the syntax.
This also includes a rework for error recovery in the parser. This is now just possible for file_input parsing, which means for full files.
Includes also a refactoring of the tokenizer. No more do we have to add an additional newline, because it now works correctly (removes certain confusion.
2015-12-20 22:25:41 +01:00
Dave Halter
b2a691a69a PEP 484 support also means that we should evaluate comments in the future. 2015-12-19 11:10:05 +01:00
Claude
6bee214948 catch error in certain non-pep0484 annotations 2015-12-17 15:23:40 +01:00
Claude
1e6397b163 check 'assigned types'-support (comes out of the jedi-box), and add tests for that 2015-12-15 11:56:54 +01:00
Claude
3cef8b6d55 string-annotations should only be interpreted by the pep-0484 code, not the parser 2015-12-15 00:31:47 +01:00
Claude
576fdf8106 better separation pep0484 code and py__annotation__() function 2015-12-14 12:10:00 +01:00
Claude
f8debace0d forward reference pep-0484 2015-12-13 23:47:45 +01:00
Claude
7e8112d607 pep0484 return type support 2015-12-13 23:07:13 +01:00
Claude
5a8c46d509 seperate parser and testing code 2015-12-13 21:13:20 +01:00
Claude
fadf4f4419 initial poc pep-0484 type hints 2015-12-13 18:05:57 +01:00