Source base : heads/master:b75d7e2435, Aug  1 2018, 10:32:28

$ cat test.py
import timeit

queue_setup = '''
from collections import deque
q = deque()
start = 10**5
stop = start + 500
for i in range(0, stop):
    q.append(i)
'''

code = '''
index = q.index(30, 1, stop)
assert index == 30
'''
code2 = '''
index = q.index((start >> 1) + 1, start >> 1, stop >> 1)
assert index == (start >> 1) + 1
'''
code3 = '''
index = q.index(start + 1, start, stop)
assert index == start + 1
'''

repeat = 100000
print(timeit.timeit(setup = queue_setup, stmt = code, number = repeat * 20))
print(timeit.timeit(setup = queue_setup, stmt = code2, number = repeat))
print(timeit.timeit(setup = queue_setup, stmt = code3, number = repeat))

$ ./python_cur.exe test.py
2.154346022
2.899595406
5.265440983

$ ./python_ksg.exe test.py
2.1457827320000002
0.717190736
1.9934196979999999

----------------------

I'm not sure what your proposal is. Do you have a patch that increases the performance of collections.deque in some cases?  If so please share that patch, preferably as a pull request on GitHub (see <https://devguide.python.org/pullrequest/> for an explanation).

Sorry, I'm waiting for permit CLA signing.
I will request PR after CLA was signed.

That's ok, I hadn't expected that you'd sign the CLA before being asked to do so :-)

Good luck.

Why are we getting multiple tracker items opening and closing for this at the same time?  Something odd is happening.  Please don't close the tracker and change user ids in the middle of a conversation:

   https://bugs.python.org/issue34298
   https://bugs.python.org/issue34295

I thing so too, it's my fault.

It looks like deque.index() now has a fast searcher.