Nick Coghlan wrote: > 1. Making "docstring" an attribute of the Function node rather than > leaving it embedded as the first statement in the suite (this avoids > issues where AST-based constant folding could potentially corrupt the > docstring) > 2. Collapsing Num, Str, Bytes, Ellipsis into a single Literal node > type (the handling of those nodes is the same in a lot of cases) > 3. Since they're keywords now, pick up True, False, None at the > parsing stage and turn them into instances of the Literal node type, > allowing the current Name-based special casing to be removed. These all sound good to me. -- Greg
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4