Futures on responses
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- networking
Research direction
The issue does not name files, tests, or an entry point. Start by reviewing the concurrent.futures, Requests futures, and Tornado Async HTTP Client references, then determine the intended client approach; completion criteria are not defined in the issue.
Written by the indexing model from the issue text.
Description
We've done a bit of musing on how we would use concurrent.futures within a Python 3 version of multyvac/cloud.
This would mean that our underlying network client would need to use either:
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
lexiforest/curl_cffi#864 ·
Maintainers usually reply within 1 day
-
effort:low model:light plan planner:opus-5-5 tests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ZcashFoundation/zeeder#106 ·
-
Add `foxit.com`Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
v2fly/domain-list-community#4092 ·
Maintainers usually reply within 2 days