Terry J. Reedy added the comment:
I managed to crash 2.7 -n by running the multi-thread tkinter program posted
for #10909. Since it modifies widgets created in the main thread from a
thread, I don't consider the failure a fixable IDLE bug.
3.6 -n ran the same program, so this is only for
Martin added the comment:
Thank you very much for your help.
Specification of error :
In python 2.7.3 for Ubuntu 12.04 32-bit
It creates a program with the following line of code :
Python is a programming language That lets you work more quickly and integrate
your systems more effectively.
Terry J. Reedy added the comment:
By default, Idle runs user code in a separate process from the idle process
that runs shell and edit windows. Because connecting the two processes
sometimes fails, there is a start-up option -N (No subprocess) that run your
code in the same process as idle
Ned Deily added the comment:
That still doesn't explain the problem. How are you trying to compile the
program? For example, one way would be to use your mouse to select the Run
menu item and then the Run Module option. Or use the F5 function key shortcut
for that. Another somewhat unusual
Ned Deily added the comment:
Can you give a step-by-step sequence of commands to reproduce the problem? One
thing that looks somewhat suspicious is that there seem to be multiple IDLE
*Python Shell windows open. Normally there should only be one.
--
nosy: +ned.deily
title: python
Martin added the comment:
I have three shell windows open because everytime i run the code corrected, it
opens a new shell, I try to close them but there is one that keeps open, unless
I kill it by terminal (kill) I attach a photo of compiling the line of code,
closing leftover shell ... What
