[issue34295] Avoid inefficient way to find start point in deque.index

Raymond Hettinger added the comment: OP closed the PR. -- resolution: -> rejected stage: patch review -> resolved status: open -> closed versions: -Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7 ___ Python tracker

[issue34295] Avoid inefficient way to find start point in deque.index

New submission from Raymond Hettinger : Can you run some timings to show the difference. Also, you need to sign a CLA. -- assignee: -> rhettinger nosy: +rhettinger ___ Python tracker ___

[issue34295] Avoid inefficient way to find start point in deque.index

Change by Seonggi Kim : -- components: +Extension Modules -ctypes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue34295] Avoid inefficient way to find start point in deque.index

Change by Seonggi Kim : -- keywords: +patch pull_requests: +8097 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue34295] Avoid inefficient way to find start point in deque.index

Change by Seonggi Kim : -- components: ctypes nosy: hacksg priority: normal severity: normal status: open title: Avoid inefficient way to find start point in deque.index type: enhancement versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8 _