Raymond Hettinger <rhettin...@users.sourceforge.net> added the comment:
Please take care in presenting timings. It is easy to get misleading results: * Factor-out the attribute lookup time (since that isn't the part being changed: -s 'c = range(1000000); c_ins=c.insert; c_pop=c.pop' 'c_insert(0, c_pop())' * The case of alternately prepending and the popping the 0th element is atypical. Trying prepending many, then popping many. Trying popping first, then prepending. * The patch needs to be throughly exercised so that we cover all of the expected behaviors (do many prepends trigger memmoves, do many prepops leave tons of unused space, what happens with the normal case of a moving queue where the average size varies but hovers around a typical mean). A decision cannot be based on exercising a small fragment of a data structure on just the things it is good at. What happens to other typical list behavior and lookup times, etc? ---------- nosy: +rhettinger _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7784> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
