unittest: unhelpful truncating of long strings.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
The issue points to unittest's handling of long strings but names no file, entry point, or test. Start by locating the relevant unittest behavior and existing tests, then clarify the expected truncation and verify that the resulting output is useful.
Written by the indexing model from the issue text.
Description
| BPO | 21820 |
|---|---|
| Nosy | @ncoghlan, @larryhastings, @rbtcollins, @cjw296, @ezio-melotti, @bitdancer, @voidspace, @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 = None
closed_at = None
created_at = <Date 2014-06-21.10:34:46.122>
labels = ['3.7', '3.8', 'type-bug', 'tests', '3.9']
title = 'unittest: unhelpful truncating of long strings.'
updated_at = <Date 2019-12-06.23:08:38.949>
user = 'https://github.com/cjw296'
bugs.python.org fields:
activity = <Date 2019-12-06.23:08:38.949>
actor = 'Ella Sharakanski'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2014-06-21.10:34:46.122>
creator = 'cjw296'
dependencies = []
files = []
hgrepos = []
issue_num = 21820
keywords = ['3.4regression']
message_count = 12.0
messages = ['221167', '221169', '221170', '221345', '221355', '221356', '221361', '221397', '221398', '221473', '341885', '357953']
nosy_count = 9.0
nosy_names = ['ncoghlan', 'larry', 'rbcollins', 'cjw296', 'ezio.melotti', 'r.david.murray', 'michael.foord', 'serhiy.storchaka', 'Ella Sharakanski']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue21820'
versions = ['Python 3.7', 'Python 3.8', 'Python 3.9']
- 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