doctest syntax ambiguity between continuation line and ellipsis
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- testing-qa
Research direction
The issue names doctest but provides no implementation file, test, or concrete expected syntax. Start by locating doctest's parser and existing tests, then compare continuation-line and ellipsis handling against the reported ambiguity. Done should be defined by a regression test and an agreed, unambiguous behavior.
Written by the indexing model from the issue text.
Description
| BPO | 32509 |
|---|---|
| Nosy | @tim-one, @jaraco, @stevendaprano, @bitdancer, @mblahay |
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 2018-01-07.04:05:17.271>
labels = ['3.8', 'type-bug', 'library']
title = 'doctest syntax ambiguity between continuation line and ellipsis'
updated_at = <Date 2021-02-08.00:11:09.958>
user = 'https://github.com/jaraco'
bugs.python.org fields:
activity = <Date 2021-02-08.00:11:09.958>
actor = 'jaraco'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-01-07.04:05:17.271>
creator = 'jaraco'
dependencies = []
files = []
hgrepos = []
issue_num = 32509
keywords = []
message_count = 15.0
messages = ['309599', '309600', '309601', '309602', '309603', '309604', '309605', '309606', '309611', '309622', '309630', '309631', '342372', '385154', '386610']
nosy_count = 5.0
nosy_names = ['tim.peters', 'jaraco', 'steven.daprano', 'r.david.murray', 'mblahay']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue32509'
versions = ['Python 3.8']
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100