12 comments

[ 0.50 ms ] story [ 45.2 ms ] thread
4-part series on writing a Python debugger from scratch, using old and new APIs.
You should consider prefixing your articles with Show HN: so they get better attention and even more direct feedback.

I'm assuming this might be your work anyway, feel free to correct me if I'm wrong.

As an aside, I've bookmarked the article, this feels like something that will provide some insight into Python specifics I had no idea existed.

Show HN is not really for serial writing or most types of online reading material. Take a look at https://news.ycombinator.com/showhn.html
I agree, but it's also a good idea to post a comment explaining you are the author as the OP did.
Thank you, it was my first submission :)
Probably better to be a little more explicit than a summary of what the page is about (lots of people habitually paste these in, whether they are the author or not) if you want to post a first comment - I'm the author, ask me things, here's an interesting bit from article, etc. You can also skip it, of course, but you know. Be you, don't be a tldr :)
(comment deleted)
(comment deleted)
I like this kind of posting and thanks first. It is important to learn by teaching others.

May I ask why 3.12. Just read here how marvellous that release is for scipy. Is that something big happen in 3.12. Still on 3.9 due to Pygame.

Python 3.12 adds a new events API useful for debugging:

    PEP 669 defines a new API for profilers, debuggers, and other tools to monitor events in CPython. It covers a wide range of events, including calls, returns, lines, exceptions, jumps, and more. This means that you only pay for what you use, providing support for near-zero overhead debuggers and coverage tools. See sys.monitoring for details.
3.12 adds new APIs (see blog post), but there are 3 other parts of the series that use an older Python API.
Brilliant series! Are there any similar articles on how to make a Javascript debugger?