[issue35664] Optimize itemgetter()

2019-01-07 Thread Raymond Hettinger
Change by Raymond Hettinger : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue35664] Optimize itemgetter()

2019-01-07 Thread Raymond Hettinger
Raymond Hettinger added the comment: New changeset 2d53bed79c1953390f85b191c72855e457e09305 by Raymond Hettinger in branch 'master': bpo-35664: Optimize operator.itemgetter (GH-11435) https://github.com/python/cpython/commit/2d53bed79c1953390f85b191c72855e457e09305 --

[issue35664] Optimize itemgetter()

2019-01-04 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Please provide microbenchmark results also for the following cases: * Negative index with tuple. * Slice index with tuple. * Tuple subclass. * List. * Large (2**61 and -2**61) index. I do not expect significant regression, but if it is, we should be aware.

[issue35664] Optimize itemgetter()

2019-01-04 Thread Raymond Hettinger
Change by Raymond Hettinger : -- keywords: +patch, patch, patch pull_requests: +10865, 10866, 10867 stage: -> patch review ___ Python tracker ___

[issue35664] Optimize itemgetter()

2019-01-04 Thread Raymond Hettinger
Change by Raymond Hettinger : -- keywords: +patch, patch pull_requests: +10865, 10866 stage: -> patch review ___ Python tracker ___

[issue35664] Optimize itemgetter()

2019-01-04 Thread Raymond Hettinger
Change by Raymond Hettinger : -- keywords: +patch pull_requests: +10865 stage: -> patch review ___ Python tracker ___ ___

[issue35664] Optimize itemgetter()

2019-01-04 Thread Raymond Hettinger
New submission from Raymond Hettinger : Improve performance by 33% by optimizing argument handling and by adding a fast path for the common case of a single non-negative integer index into a tuple (which is the typical use case in the standard library). -- components: Library (Lib)