What should the error message in the exception raised by assertTrue and assertFalse be?
Open
Nobody has claimed this yet.
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38706 |
|---|---|
| Nosy | @terryjreedy, @mdickinson, @rbtcollins, @ezio-melotti, @stevendaprano, @bitdancer, @voidspace, @encukou, @serhiy-storchaka, @ammaraskar, @brandtbucher, @michael-karotsieris |
| PRs |
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 2019-11-05.21:16:18.934>
labels = ['type-feature', 'library', '3.9']
title = 'What should the error message in the exception raised by assertTrue and assertFalse be?'
updated_at = <Date 2019-12-06.11:51:47.142>
user = 'https://github.com/michael-karotsieris'
bugs.python.org fields:
activity = <Date 2019-12-06.11:51:47.142>
actor = 'steven.daprano'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-11-05.21:16:18.934>
creator = 'mkarotsieris'
dependencies = []
files = []
hgrepos = []
issue_num = 38706
keywords = ['patch']
message_count = 17.0
messages = ['356065', '356067', '356081', '356082', '356083', '356103', '356104', '356105', '356114', '356120', '356124', '356126', '356179', '356206', '356208', '356211', '357911']
nosy_count = 12.0
nosy_names = ['terry.reedy', 'mark.dickinson', 'rbcollins', 'ezio.melotti', 'steven.daprano', 'r.david.murray', 'michael.foord', 'petr.viktorin', 'serhiy.storchaka', 'ammar2', 'brandtbucher', 'mkarotsieris']
pr_nums = ['17049', '17073']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue38706'
versions = ['Python 3.9']
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 reviewing the issue discussion and the referenced pull requests python/cpython#17049 and #17073; no source file or test is named in the payload. Done means reaching an agreed error-message specification for assertTrue and assertFalse, then validating it against the existing review work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100