Bad formatting in WinError 193 when using subprocess.check_call

Open
#70,680 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

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.

Written by the indexing model from the issue text.

Description

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']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.