KeyboardInterrupt handling and traceback broken on Windows 10

Open
#69,563 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No files or tests are named. Start by reproducing the KeyboardInterrupt and traceback behavior on Windows 10, then inspect the interpreter-core handling involved; done means interruption handling and traceback output work correctly on the affected platform.

Written by the indexing model from the issue text.

Description

interpreter-core OS-windows type-bug
BPO 25376
Nosy @pfmoore, @tjguk, @bitdancer, @vadmium, @zware, @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 2015-10-11.12:32:24.874>
labels = ['interpreter-core', 'type-bug', 'OS-windows']
title = 'KeyboardInterrupt handling and traceback broken on Windows 10'
updated_at = <Date 2015-10-13.04:40:06.506>
user = 'https://bugs.python.org/mdf'

bugs.python.org fields:

activity = <Date 2015-10-13.04:40:06.506>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core', 'Windows']
creation = <Date 2015-10-11.12:32:24.874>
creator = 'mdf'
dependencies = []
files = []
hgrepos = []
issue_num = 25376
keywords = []
message_count = 5.0
messages = ['252800', '252801', '252805', '252816', '252912']
nosy_count = 7.0
nosy_names = ['paul.moore', 'tim.golden', 'r.david.murray', 'martin.panter', 'zach.ware', 'steve.dower', 'mdf']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25376'
versions = ['Python 3.4', 'Python 3.5']

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.