Repository navigation
Idle terminates on source save while debugging #50506
Description
| BPO | 6257 |
|---|---|
| Nosy | @serwy |
| Superseder |
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 = <Date 2012-07-18.22:22:04.064>
created_at = <Date 2009-06-10.16:47:13.056>
labels = ['expert-IDLE', 'type-crash']
title = 'Idle terminates on source save while debugging'
updated_at = <Date 2012-07-18.22:22:04.011>
user = 'https://bugs.python.org/andyharrington'bugs.python.org fields:
activity = <Date 2012-07-18.22:22:04.011>
actor = 'roger.serwy'
assignee = 'none'
closed = True
closed_date = <Date 2012-07-18.22:22:04.064>
closer = 'roger.serwy'
components = ['IDLE']
creation = <Date 2009-06-10.16:47:13.056>
creator = 'andyharrington'
dependencies = []
files = []
hgrepos = []
issue_num = 6257
keywords = []
message_count = 5.0
messages = ['89217', '103178', '165809', '165814', '165816']
nosy_count = 3.0
nosy_names = ['andyharrington', 'roger.serwy', 'JimShaw']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = None
status = 'closed'
superseder = '9803'
type = 'crash'
url = 'https://bugs.python.org/issue6257'
versions = ['Python 3.1']
Activity
andyharrington commentedon Jun 10, 2009
When I am running the idle debugger, and change something in a source
file and save it, the save works but idle immediately closes.
I can see the debugger not liking it, but it would be much better if
just the debugger stopped, not the whole idle environment.
I'm running XP professional, Python 3.0.1
JimShaw commentedon Apr 15, 2010
I am having the same problem with Windows Vista and Windows 7.
serwy commentedon Jul 18, 2012
The only was I get IDLE to crash is if the file has breakpoints enabled. Is this how IDLE is crashing?
andyharrington commentedon Jul 18, 2012
yes I certainly used breakpoints
On Wed, Jul 18, 2012 at 4:50 PM, Roger Serwy <report@bugs.python.org> wrote:
serwy commentedon Jul 18, 2012
Thanks Andy for your prompt response.
This issue is a duplicate with bpo-9803 which has a patch. I will close this issue in favor of that one. Feel free to add yourself to the nosy list if you wish.