timeit documentation should describe caveats
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
Start by locating the timeit documentation and review the linked BPO issue, including its six-message history, to identify the caveats that need coverage. Update the documentation so those caveats are explicitly described, then verify the resulting text in the relevant documentation build or review process.
Written by the indexing model from the issue text.
Description
| BPO | 32039 |
|---|---|
| Nosy | @warsaw, @rhettinger, @vstinner, @serhiy-storchaka |
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 = 'https://github.com/warsaw'
closed_at = None
created_at = <Date 2017-11-15.19:43:16.439>
labels = ['3.7', 'docs']
title = 'timeit documentation should describe caveats'
updated_at = <Date 2017-11-23.13:12:53.767>
user = 'https://github.com/warsaw'
bugs.python.org fields:
activity = <Date 2017-11-23.13:12:53.767>
actor = 'serhiy.storchaka'
assignee = 'barry'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2017-11-15.19:43:16.439>
creator = 'barry'
dependencies = []
files = []
hgrepos = []
issue_num = 32039
keywords = []
message_count = 6.0
messages = ['306303', '306310', '306314', '306315', '306327', '306815']
nosy_count = 4.0
nosy_names = ['barry', 'rhettinger', 'vstinner', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue32039'
versions = ['Python 3.6', 'Python 3.7']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
zostera/django-bootstrap4#894 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3276 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
zilliztech/memsearch#759 ·