StubTreq should get its mind right about what interface it's a replacement for

Open
#243 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by reading issue #242 and locating the definition and usages of StubTreq in the repository. Determine which HTTPClient interface it currently represents and identify the compatibility and deprecation work needed; done means StubClient replaces StubTreq without leaving unresolved references.

Written by the indexing model from the issue text.

Description

Apropos of #242: is StubTreq a treq or an HTTPClient ? It's confused about this.

We should deprecate StubTreq itself and replace it with StubClient.

Dominant language
Python
Stars
603
Forks
140
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from twisted/treq

All issues in twisted/treq

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.