This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kj
Recipients acdha, bob.ippolito, ezio.melotti,, kj, lisroach, pitrou, r.david.murray, rhettinger, serhiy.storchaka
Date 2020-11-05.15:47:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Sorry to butt into this conversation, but I wanted to add that I have interest in this feature - deques are the fourth most common container types I use in Python. Is there any way I can help to get this PR across the finish line?

So far I've forked the PR, rebased it, then applied some changes (docs, news, and performance) to try to lessen the impact of checking for deque:

(Python/master branch)
>>> timeit.timeit(stmt="json.dumps(['test'])", setup="import json", number=1_000_000)

>>> timeit.timeit(stmt="json.dumps(10000)", setup="import json", number=1_000_000)

(Python/pr_830 branch)
>>> timeit.timeit(stmt="json.dumps(['test'])", setup="import json", number=1_000_000)

>>> timeit.timeit(stmt="json.dumps(10000)", setup="import json", number=1_000_000)

The PR branch is here

I'm not a Git wizard, so I don't know what's the best next step. Do I 
a. Make a PR against Lisa's PR (or)
b. Make a brand new PR against cpython master ?

If the core devs here feel that after 6 years, this change might be unneeded after all, I don't mind closing the branch either. Thanks for reading.
Date User Action Args
2020-11-05 15:47:24kjsetrecipients: + kj, rhettinger, bob.ippolito, pitrou, ezio.melotti, r.david.murray,, serhiy.storchaka, acdha, lisroach
2020-11-05 15:47:24kjsetmessageid: <>
2020-11-05 15:47:24kjlinkissue20774 messages
2020-11-05 15:47:23kjcreate