Currently attending #PyConUS2022 @pyblogsal on Making Python better one error message at a time.
(Not sure i'll be able to live-tweet but will try. Pablo speaks very fast!)
(Not sure i'll be able to live-tweet but will try. Pablo speaks very fast!)
#PyConUS2022 @pyblogsal Syntax errors are important. They impact developer time.
Pablo shows several examples of SyntaxErrors prior to Python 3.9 that weren't helpful. The error simply says "invalid syntax", when the real problems are things like not closing "}" or ")"
Pablo shows several examples of SyntaxErrors prior to Python 3.9 that weren't helpful. The error simply says "invalid syntax", when the real problems are things like not closing "}" or ")"
#PyConUS2022 @pyblogsal The new PEG parser (from PEP 617) replaces the parsing in CPython, co-authored by @pyblogsal @lysnikolaou @gvanrossum
The original parser was written in 1990.
The original parser was written in 1990.
#PyConUS2022 @pyblogsal With the new PEG parser, now the SyntaxError is able to provide more helpful error messages! It tells you: '{' was never closed 👏🏻
#PyConUS2022 @pyblogsal
AttributeError has also been problematic. Ever seen the error 'NoneType' is not subscriptable?
In Python 3.11 it tells you which one it is!
AttributeError has also been problematic. Ever seen the error 'NoneType' is not subscriptable?
In Python 3.11 it tells you which one it is!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
