Mark T. Tomczak<p>Debugging a complex Python library via a Jupyter notebook is <em>unfairly good</em> tech, yinz.</p><p>Now that I've tried it, I can't go back.</p><p>My favorite part of this exercise?</p><p>Testing the fix in-place by copying the broken method out of the class, editing it, monkey-patching it back into the class definition, and then re-running the small verification setup I threw together in Jupyter. Newly-created class instances are using the new method and the flow goes from "Busted" to "Working."</p><p>(Plus, Jupyter supports matplotlib output, which is huge when what I'm debugging is fundamentally geometric in nature).</p><p><a href="https://mastodon.fixermark.com/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a> <a href="https://mastodon.fixermark.com/tags/jupyter" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>jupyter</span></a> <a href="https://mastodon.fixermark.com/tags/matplotlib" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>matplotlib</span></a> <a href="https://mastodon.fixermark.com/tags/shapely" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>shapely</span></a></p>