Adding unittest for cProfile / profile command line interface
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 30118 |
|---|---|
| Nosy | @serhiy-storchaka, @mlouielu |
| PRs |
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 2017-04-20.15:39:27.176>
labels = ['3.7', 'library']
title = 'Adding unittest for cProfile / profile command line interface'
updated_at = <Date 2017-04-21.09:00:40.560>
user = 'https://github.com/mlouielu'
bugs.python.org fields:
activity = <Date 2017-04-21.09:00:40.560>
actor = 'louielu'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-04-20.15:39:27.176>
creator = 'louielu'
dependencies = []
files = []
hgrepos = []
issue_num = 30118
keywords = []
message_count = 1.0
messages = ['291981']
nosy_count = 2.0
nosy_names = ['serhiy.storchaka', 'louielu']
pr_nums = ['1232']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue30118'
versions = ['Python 3.7']
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 inspecting the cProfile and profile command-line interfaces and the existing library test layout; the issue names no file or test path. Done means adding unittest coverage for both command-line interfaces, although PR #1232 is already listed in the issue metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100