Raymond Hettinger added the comment: Jesús, I backported this to 2.7 because it was affecting intended usability of multiple parts of the API. The current code had the egregious and unintended side-effect of touching every data element during a rotate -- this resulted in a huge number of unnecessary cache line misses and was blowing useful data out of cache.
IMO, a performance bug is different from a micro-optimization, especially if it is affecting the intended uses for part of an API. Serhiy, you're welcome to backport to 3.3 if you desire. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16398> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
