doctest cause warnings in tests using generators
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 28/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- testing-qa
Research direction
Start by reviewing the three linked doctest.txt files, especially the spurious-warning and corrected examples, then reproduce the generator-related warning described in issue 21178. Compare the examples to determine what test behavior needs changing; done means the relevant doctest runs without the unintended warning while preserving the corrected case.
Written by the indexing model from the issue text.
Description
| BPO | 21178 |
|---|---|
| Nosy | @terryjreedy, @ncoghlan, @iritkatriel |
| Files |
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 2014-04-08.10:49:06.857>
labels = ['type-bug', 'tests', '3.9', '3.10', '3.11']
title = 'doctest cause warnings in tests using generators'
updated_at = <Date 2021-12-10.18:23:29.804>
user = 'https://bugs.python.org/oluensdorf'
bugs.python.org fields:
activity = <Date 2021-12-10.18:23:29.804>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2014-04-08.10:49:06.857>
creator = 'oluensdorf'
dependencies = []
files = ['34760', '34761', '34790']
hgrepos = []
issue_num = 21178
keywords = []
message_count = 5.0
messages = ['215750', '215755', '215948', '215965', '408239']
nosy_count = 4.0
nosy_names = ['terry.reedy', 'ncoghlan', 'oluensdorf', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue21178'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
- 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 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·
-
link-check link-check:sphinx-theme
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
modelscope/DiffSynth-Studio#1702 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OpenHands/extensions#626 · 1 comment ·