Learnings

<p>Debugging Tips And Techniques: </p>

<p>The Saff Squeeze: </p>

How to recover lost Python source code if it's still resident in-memory:

<p>Django: How can I see a list of urlpatterns? </p>

<p>Render HTML from a string to browser straight from Python (useful for debugging broken template/view tests!) </p>

<p>Pyroscope: an open source continuous profiling platform </p>

<p>Scalene: a high-performance, high-precision CPU, GPU, and memory profiler for Python </p>

<p>Log all queries of Postgres on docker-compose: </p>

<p>If you're in a pdb/ipdb session and need to step into an interactive code call, use the <code>debug</code> command. This way, when you type <code>debug xpto()</code>, you'll start debugging whatever code chunk you may want to.</p>

<p>Javascript debugger statement </p>

<p>Quickly debugging Postgres problems: </p>

<p>Console.table() - Displays tabular data as a table. </p>

<p>Debugging-friendly tracebacks for Python: </p>

<p>Never use print for debugging again: </p>

<p>ipdb can also be used when debugging issues with environments other than your local one. <code>ipdb.runcall</code> helps one debug issues on method calls through and IPython shell, and it's as simple as:</p> <p>```</p> <blockquote> <blockquote> <blockquote> <p>import ipdb import xpto_method # the method one wants to debug ipdb.runcall(xpto_method, 'method arg') (ipdb) ... ```</p> </blockquote> </blockquote> </blockquote> <p><code>ipdb.runcall</code> receives the method one wants to call as the first argument, and subsequent to that the target method arguments.</p> <p>For more usage examples, check: </p>

<p>Debugging code called by celery tasks with rdb #debugging-tasks-remotely-using-pdb</p>

<p>Colors in JavaScript console: </p>

<p>Use <code>console.table()</code> to display tabular data in a web console: </p>

<p>Type <code>interact</code> inside a pdb session to start a shell where you can paste multiline statements</p>

<p>Great blog post on Python pdb: <a href="#.xogl073gi">#.xogl073gi</a></p>