Don't use bare excepts
Open
Nobody has claimed this yet.
core
new
priority-normal
task
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@hawkowl reported |
|---|---|
| Trac ID | trac#9500 |
| Type | task |
| Created | 2018-07-24 11:17:07Z |
We likely shouldn't be doing this anywhere.
Searchable metadata
trac-id__9500 9500
type__task task
reporter__hawkowl hawkowl
priority__normal normal
milestone__None None
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__None None
time__1532431027286349 1532431027286349
changetime__1532431027286349 1532431027286349
version__None None
owner__None None
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
No files or tests are named. Start by searching the Twisted repository for bare Python except clauses, then inspect each occurrence in the core component and its surrounding tests. Done means the repository no longer uses bare excepts and the relevant test suite still passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100