MP 163: Probably not as many as you think! Many of us who marvel at the wonder of mathematical constants just enjoyed another pi day. This year's celebration had me thinking about how we decide how many digits of pi to use whenever we're working with
MP 162: It's been answered many times, but it's always worth revisiting. I've been reflecting on classes lately, and how we teach them. One of the questions that comes up in every discussion about OOP with people who are seeing it for the first
MP 161: Autonomous agents slandering open source maintainers is almost certainly just a beginning. In case you missed it, we reached another inflection point in the ever-increasing impact of AI on society last week. Briefly, an autonomous agent submitted a PR on the Matplotlib repository. That PR was rejected, because
MP 160: When we're discussing functions in Python, what do we call the different parts? I've been reflecting on typing in Python recently. I haven't used type hints much, because all my programs have worked fine without them. But typing in Python has matured
MP 159: What did we learn about debugging from this series? What can you do to continue this work? Note: This post is part of an ongoing series about debugging in Python. The posts in this series will only be available to paid subscribers for the first 6 weeks. After
MP 158: Fixing a recursion bug that only shows up after many consecutive games. Note: This post is part of an ongoing series about debugging in Python. The posts in this series will only be available to paid subscribers for the first 6 weeks. After that they will be available
MP 157: It's so much easier now! Back in August, I wrote a post about using uv to manage my overall Python environment, after years of using pyenv. One of the claims in that post was that it should be much easier to keep my environment updated over
MP 156: Implementing the computer's turn, and recognizing the end of the game. Note: This post is part of an ongoing series about debugging in Python. The posts in this series will only be available to paid subscribers for the first 6 weeks. After that they will be
MP 155: Using an IDE debugger to understand a program's internal behavior. Note: This post is part of an ongoing series about debugging in Python. The posts in this series will only be available to paid subscribers for the first 6 weeks. After that they will be available
MP 154: They just keep coming. :) Note: This post is part of an ongoing series about debugging in Python. The posts in this series will only be available to paid subscribers for the first 6 weeks. After that they will be available to everyone. Thank you to everyone who supports
MP 153: If it's not already, it should be. :) Note: I will get back to the debugging series as soon as I can. Work has been busy lately, and it's much easier to write about things that are coming up in my regular work at the
MP 152: But the timedelta implementation in Python is correct. In many projects, timestamps are just a bit of metadata you might look at once in a while when troubleshooting. But sometimes, timestamps are a critical piece of information. If you handle them right, your project works. If you don&