smtplib is glitchy after receive server code 500
未關閉
還沒有人認領這個 Issue。
3.7 (EOL)
topic-email
type-bug
- 主要語言
- Python
- 星號
- 77.2k
- 分支
- 36k
- PR 合併指標
- PR 指標待擷取
描述
| BPO | 42498 |
|---|---|
| Nosy | @warsaw, @bitdancer, @pepoluan |
| 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 2020-11-29.05:30:35.881>
labels = ['3.7', 'expert-email', 'type-crash']
title = 'smtplib is glitchy after receive server code 500'
updated_at = <Date 2021-01-05.19:01:17.663>
user = 'https://bugs.python.org/izomiac'
bugs.python.org fields:
activity = <Date 2021-01-05.19:01:17.663>
actor = 'izomiac'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2020-11-29.05:30:35.881>
creator = 'izomiac'
dependencies = []
files = ['49634']
hgrepos = []
issue_num = 42498
keywords = []
message_count = 3.0
messages = ['382038', '384373', '384426']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'izomiac', 'pepoluan']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue42498'
versions = ['Python 3.7']
貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
研究方向
從附件 debug output.txt 開始，追蹤伺服器回傳代碼 500 後涉及的 smtplib 電子郵件路徑。根據連線記錄判斷預期行為，然後針對該失敗情境驗證 fix；如果能夠識別相關的測試位置，則新增覆蓋測試。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- python
- 領域
- backend
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 28/100