Refactoring exception hierarchy
Open
Nobody has claimed this yet.
Breaking API Change
Needs BDFL Input
- Dominant language
- Python
- Stars
- 54.3k
- Forks
- 10.4k
- Avg merge
- 16h 43m
- Merged PRs (30d)
- 3
Description
This was mentioned in #2230 as a project for requests 3.0, but it probably should get its own thread.
I wrote a lot of words about what I'd like exception hierarchy to look like, here:
Contributor guide
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.
Research direction
Start by reading the proposal in the linked gist and the context in issue #2230. Confirm the intended exception hierarchy and its scope before locating the affected Requests code; done means the agreed hierarchy is implemented consistently and the relevant behavior remains covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100