This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author aroberge
Recipients aroberge, pablogsal
Date 2021-02-04.00:15:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1612397743.76.0.674707599219.issue43121@roundup.psfhosted.org>
In-reply-to
Content
Pablo: to run the friendly-traceback test suite is simply a matter of typing "pytest" from the root directory of the repository (after installing the dependencies). However, it would not be helpful for the purpose of CPython development, as likely more failing tests would be due to Friendly-traceback itself.

As a first step, Friendly-traceback tries to make use of the information given by Python (for example, the new "expected ':'"); if it does not recognize the message, or if the message is "invalid syntax", it uses some heuristics to guess what might be the probable cause. 

Improvements to the messages given by CPython are likely going to initially result in failed tests for Friendly-traceback, whether the information provided by CPython is valid (most of the time) or not.

The test suite I use includes things that I imagine a beginner might write. For example, using "else if" instead of "elif".  With one of the newest additions of CPython ("expected ':'") which is accurate in most cases, this specific unit test would likely fail until I make the appropriate adjustement to Friendly-traceback.
History
Date User Action Args
2021-02-04 00:15:43arobergesetrecipients: + aroberge, pablogsal
2021-02-04 00:15:43arobergesetmessageid: <1612397743.76.0.674707599219.issue43121@roundup.psfhosted.org>
2021-02-04 00:15:43arobergelinkissue43121 messages
2021-02-04 00:15:42arobergecreate