[Python-Dev] Possible optimization for LOAD_FAST ? (original) (raw)
Cesare Di Mauro cesare.di.mauro at gmail.com
Fri Dec 31 18:51:39 CET 2010
- Previous message: [Python-Dev] Possible optimization for LOAD_FAST ?
- Next message: [Python-Dev] Possible optimization for LOAD_FAST ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2010/12/31 <skip at pobox.com>
>> Another example. I can totally remove the variable i, just using the >> stack, so a debugger (or, in general, having the tracing enabled) >> cannot even find something to change about it. Ethan> -1 Ethan> Debugging is challenging enough as it is -- why would you want to Ethan> make it even more difficult? I don't know. Maybe he wants his program to run faster.
:D
"Aggressive" optimizations can be enabled with explicit options, in order to leave normal "debugger-prone" code.
If you use print statements for the bulk of your debugging (many people do), unrolling loops doesn't affect your debugging ability.
Skip
It's a common practice. Also IDEs helps a lot, and advanced interactive shells too (such as DreamPie).
Cesare -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20101231/21907f08/attachment.html>
- Previous message: [Python-Dev] Possible optimization for LOAD_FAST ?
- Next message: [Python-Dev] Possible optimization for LOAD_FAST ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]