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 rhettinger, sir-sigurd, vstinner
Date 2019-02-20.06:47:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Zeroing memory is usually not expensive relative to the cost of filling it in.  Also, the timing loop is unrealistic.  We mostly care about small tuples.  

For long term maintenance of the project, I recommend filling the code with these unsafe variants which will segfault whenever someone follows the normal practice of decreffing when an error is encountered.  This would be yet another special case a person would have to learn to do maintenance or code review for CPython.

In general, there are a lot of small optimizations to be had if we were to forgo principles of loose coupling, defensive programming, and ease of maintenance.  Once in a while, we find one that actually is worth it, but usually it is a best practice sprinkle these special cases all over the code (see MS Code Complete for more discussion on the long term costs of this kind of coding).
Date User Action Args
2019-02-20 06:47:28rhettingersetrecipients: + rhettinger, vstinner, sir-sigurd
2019-02-20 06:47:28rhettingersetmessageid: <>
2019-02-20 06:47:28rhettingerlinkissue36030 messages
2019-02-20 06:47:28rhettingercreate