Showing content from http://mail.python.org/pipermail/python-dev/attachments/20101231/21907f08/attachment.html below:
2010/12/31 <span dir="ltr"><<a href="mailto:skip@pobox.com">skip@pobox.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
>> Another example. I can totally remove the variable i, just using the<br>
>> stack, so a debugger (or, in general, having the tracing enabled)<br> >> cannot even find something to change about it.</div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Ethan> -1<br>
<br>
Ethan> Debugging is challenging enough as it is -- why would you want to<br>
Ethan> make it even more difficult?<br>
<br>
<snarky><br>
I don't know. Maybe he wants his program to run faster.<br> </snarky><br></blockquote><div><br></div><div>:D</div><div><br></div><div>"Aggressive" optimizations can be enabled with explicit options, in order to leave normal "debugger-prone" code.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
If you use print statements for the bulk of your debugging (many people do),<br>
unrolling loops doesn't affect your debugging ability.<br>
<br> Skip</blockquote><div><br></div><div>It's a common practice. Also IDEs helps a lot, and advanced interactive shells too (such as DreamPie).</div><div><br>Cesare<br></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4