doctest terminates when accessing __wrapped__ raises an error
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- testing-qa
Research direction
Reproduce the failure using the linked sample shell session and unwrapable_ob.py, then inspect PR #14756 and the doctest tests area for the existing direction. Done means doctest no longer terminates when accessing wrapped raises an error, with the behavior covered by a test.
Written by the indexing model from the issue text.
Description
| BPO | 25998 |
|---|---|
| Nosy | @stevendaprano, @bitdancer, @jstasiak, @BoboTiG |
| PRs | |
| 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 2016-01-02.22:30:43.610>
labels = ['type-bug', 'tests']
title = 'doctest terminates when accessing __wrapped__ raises an error'
updated_at = <Date 2019-07-13.16:45:13.678>
user = 'https://bugs.python.org/LasseSchuirmann'
bugs.python.org fields:
activity = <Date 2019-07-13.16:45:13.678>
actor = 'Tiger-222'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2016-01-02.22:30:43.610>
creator = 'Lasse Schuirmann'
dependencies = []
files = ['41477', '48477']
hgrepos = []
issue_num = 25998
keywords = ['patch']
message_count = 8.0
messages = ['257378', '257379', '257387', '257467', '257478', '257479', '347791', '347845']
nosy_count = 5.0
nosy_names = ['steven.daprano', 'r.david.murray', 'jstasiak', 'Lasse Schuirmann', 'Tiger-222']
pr_nums = ['14756']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25998'
versions = ['Python 3.5', 'Python 3.6']
- 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
-
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 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