unittest: unhelpful truncating of long strings.

未關閉
#66,019 12 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
35/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
python
領域
testing

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

3.7 (EOL) 3.8 (EOL) 3.9 (EOL) tests type-bug
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']

主要語言
Python
星號
77.2k
分支
36k
平均合併
1 天 9 小時
30 天內合併 PR
558

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

python/cpython 的其他 Issue

查看 python/cpython 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。