On 09.08.19 15:44, Nick Coghlan wrote: ...
However, a change like that would make the most sense when considered independently of the specific case of assignment expressions - instead, we would want to ask "What kinds of exceptions does the symbol table analysis pass raise?", and then consider whether it might make sense to define subclasses of syntax error for them.
Given the naming issue, and the fact that a potential new SyntaxError subclass would be relevant for more than just the new PEP 572 exceptions, I think the right near term approach is to go with the generic SyntaxError as Barry suggests. I'll update my PRs accordingly.
Totally agree. It is fine to have SyntaxError now and go for one or more new subclasses for a whole bunch of errors at a later time, fixing more things in a more consistent way. -- Christian Tismer :^) tismer@stackless.com Software Consulting : http://www.stackless.com/ Karl-Liebknecht-Str. 121 : https://github.com/PySide 14482 Potsdam : GPG key -> 0xFB7BEE0E phone +49 173 24 18 776 fax +49 (30) 700143-0023