This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients amaury.forgeotdarc, donmez, gideon, rhettinger
Date 2008-08-29.20:34:41
SpamBayes Score 1.8862193e-07
Marked as misclassified No
Message-id <>
Go for it.  There's really no question about fixing possible 
segfaulters.  Was just voicing my displeasure at this sort of 
exercise.  The code has been around since at least 2.2 and hasn't 
caused the slightest problem.  It bugs me to put cruft in the middle of 
otherwise tight loops.  Fortunately, the check is cheap and branch 

BTW, your timings are domained by the function call and the range(5000) 
step.  To cleanly time for-loop overhead, use:

   python -m timeit "pass"
Date User Action Args
2008-08-29 20:34:43rhettingersetrecipients: + rhettinger, amaury.forgeotdarc, donmez, gideon
2008-08-29 20:34:42rhettingersetmessageid: <>
2008-08-29 20:34:42rhettingerlinkissue3720 messages
2008-08-29 20:34:41rhettingercreate