It doesn't work!
summary
friendly (and the analysis library friendly traceback) claims to turn inscrutable Python tracebacks into a three-part explanation what, where, why and offers a www helper that opens documentation. It ships 300+ automated cases, colors and themes for IDLE mu and Jupyter, isolates the exact offending expression and prints the offending value, and supports translations. The project splits formatting (friendly) from analysis (friendly traceback) and records example tracebacks across Python versions to catch regressions.
AI-written summary · about
chapters (14)
- 0:00Start
- 3:42What the traceback tells us
- 6:33flipfloperator
- 10:17Original purpose of friendly- traceback
- 10:42Scope creep
- 12:35import
- 12:59Jupyter example
- 16:18Can a REPL be user-friendly?
- 18:58On Designing Programming Error ...
- 19:47Readability vs Usability
- 21:27None Type object is not subscriptable
- 22:23To find out more
- 23:52The future?
- 24:13Conclusion
related talks
28mGoodbye Print, Hello Debugger!
29mPeering into the black box: tips for visualizing your program's behavior
29mLiberating the Debugging Experience with the GDB Python API
29mGoodbye Print Statements, Hello Debugger!
38mHow to Read a Stack Trace
30mCode Debugging and Refactoring with OpenBugger: a Python Library for Self-Supervised AI Debuggers
24mHow we Dealt with Poor Code Analysis Support in Our Heavy Projects
31mGoodbye Print, Hello Debugger!