Bad formatting in WinError 193 when using subprocess.check_call

未关闭
#70,680 14 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
python

调研方向

The issue points to Python's subprocess.check_call handling of Windows error 193, but names no source file or test. Begin by reproducing the formatting on Windows and trace the subprocess error path; done means the error is formatted correctly and covered by a regression test.

由索引模型根据 Issue 内容生成。

描述

3.8 (EOL) OS-windows topic-subprocess type-feature
BPO 26493
Nosy @pfmoore, @tjguk, @berkerpeksag, @zware, @eryksun, @zooba

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 2016-03-06.16:56:29.691>
labels = ['type-feature', '3.8', 'OS-windows']
title = 'Bad formatting in WinError 193 when using subprocess.check_call'
updated_at = <Date 2019-05-01.18:28:25.161>
user = 'https://bugs.python.org/RalNezdeArenas'

bugs.python.org fields:

activity = <Date 2019-05-01.18:28:25.161>
actor = 'eryksun'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2016-03-06.16:56:29.691>
creator = 'Ra\xc3\xbal N\xc3\xba\xc3\xb1ez de Arenas'
dependencies = []
files = []
hgrepos = []
issue_num = 26493
keywords = []
message_count = 14.0
messages = ['261262', '261268', '261284', '261315', '261350', '261351', '341090', '341091', '341093', '341103', '341146', '341170', '341199', '341225']
nosy_count = 7.0
nosy_names = ['paul.moore', 'tim.golden', 'berker.peksag', 'zach.ware', 'eryksun', 'steve.dower', 'Ra\xc3\xbal N\xc3\xba\xc3\xb1ez de Arenas']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue26493'
versions = ['Python 3.8']

主要语言
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 摘要。