Larger and/or configurable _MAX_LENGTH for unittest messages
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 30839 |
|---|---|
| Nosy | @bitdancer |
| Dependencies |
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 2017-07-03.17:59:26.581>
labels = ['3.7', 'type-feature', 'library']
title = 'Larger and/or configurable _MAX_LENGTH for unittest messages'
updated_at = <Date 2017-07-05.20:27:37.208>
user = 'https://bugs.python.org/maarten-treewalker'
bugs.python.org fields:
activity = <Date 2017-07-05.20:27:37.208>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-07-03.17:59:26.581>
creator = 'maarten-treewalker'
dependencies = ['27432']
files = []
hgrepos = []
issue_num = 30839
keywords = []
message_count = 2.0
messages = ['297605', '297779']
nosy_count = 2.0
nosy_names = ['r.david.murray', 'maarten-treewalker']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue30839'
versions = ['Python 3.7']
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.
Research direction
Start by reading unittest's assertion-message truncation behavior and the linked dependency, bpo-27432, to understand the existing _MAX_LENGTH handling. Define how a larger or configurable limit should affect unittest messages, then verify the behavior with focused unittest coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100