Add ability to inherit unittest argument parser
Open
Nobody has claimed this yet.
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39283 |
|---|---|
| Nosy | @tirkarthi, @https://github.com/atb00ker |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2020-01-10.04:32:18.746>
labels = ['type-bug', 'library']
title = 'Add ability to inherit unittest arguement parser'
updated_at = <Date 2020-01-21.10:12:39.221>
user = 'https://github.com/httpsgithubcomatb00ker'
bugs.python.org fields:
activity = <Date 2020-01-21.10:12:39.221>
actor = 'atb00ker'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-01-10.04:32:18.746>
creator = 'atb00ker'
dependencies = []
files = []
hgrepos = []
issue_num = 39283
keywords = []
message_count = 5.0
messages = ['359704', '359716', '359949', '360226', '360381']
nosy_count = 3.0
nosy_names = ['paul.j3', 'xtreak', 'atb00ker']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39283'
versions = []
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 linked BPO issue and the existing unittest argument-parser entry point. No files or tests are named, so identify the relevant library code and establish the expected inheritance behavior before changing anything. Done means the intended behavior is implemented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100