miniblog.

← Back to all posts
May 9, 2021 at 22:01
Python is discussing an elegant approach to tracebacks, where the subexpression that caused the exception is highlighted:
PEP 657 – Include Fine Grained Error Locations in Tracebacks | peps.python.org
PEP 657 – Include Fine Grained Error Locations in Tracebacks | peps.python.org
This PEP proposes adding a mapping from each bytecode instruction to the start and end column offsets of the line that generated them as well as the end line number. This data will be used to improve tracebacks displayed by the CPython interpreter in or...

Related Posts

Oct 5, 2022 at 00:05
This article discussing forking sqlite draws an interesting parallel between forking and the prisoner's dilemma: forking as a solo contributor is rarely successful, unless others also wish to fork! https://glaubercosta-11125.medium.com/sqlite-qemu-all-over-again-aedad19c9a1c
Sep 25, 2021 at 07:04
I've released difftastic 0.10! This version adds four new languages: C, C++, C# and Haskell! See screenshots for examples. The manual is also substantially expanded, discussing other tree diffing projects and code samples that are hard for tree diffs.
PhotoPhotoPhoto
May 31, 2021 at 05:25
scc is a fast, polished tool for counting lines of code: https://github.com/boyter/scc The author has several great posts discussing LOC tooling, including this one on exploring codebases with it:
GitHub - boyter/scc: Sloc, Cloc and Code: scc is a very fast accurate code counter with complexity calculations and COCOMO estimates written in pure Go
GitHub - boyter/scc: Sloc, Cloc and Code: scc is a very fast accurate code counter with complexity calculations and COCOMO estimates written in pure Go
Sloc, Cloc and Code: scc is a very fast accurate code counter with complexity calculations and COCOMO estimates written in pure Go - boyter/scc
Why count lines of code? | Ben E. C. Boyter