> IDLE becomes **very** unresponsive when printing long lists/strings.
> Great doses of patience and a good processor usually let you live
> through (Idle uses 100%, you have to take out of view the long text to
> make it become responsive again). At least, this happens on Windows
> (maybe oth
Kent Johnson escribió:
> Adam Gomaa wrote:
>
>> I'm having trouble with this script. When I run it, it crashes IDLE...
>> which is no fun. :(
>>
>> I'm running Ubuntu 6.06 w/ python 2.4
>>
>> When I say crash, I mean really _crash_. IDLE stop responding, and I
>> have to killall idle && killal
I'm also having trouble when running IDLE under Debian 3.1 (Kernel
2.6.12). I often run into the same problem (IDLE not responding with the
only solution to killall idle) as Adam Gomaa just after starting up IDLE
and typing in some characters.
E.g. I'm starting up IDLE and typing in "import soc" w
Adam Gomaa wrote:
> I'm having trouble with this script. When I run it, it crashes IDLE...
> which is no fun. :(
>
> I'm running Ubuntu 6.06 w/ python 2.4
>
> When I say crash, I mean really _crash_. IDLE stop responding, and I
> have to killall idle && killall python2.4 before I can restart it (
Hi Adam.
Adam Gomaa wrote:
> I'm having trouble with this script. When I run it, it crashes IDLE...
> which is no fun. :(
>
> I'm running Ubuntu 6.06 w/ python 2.4
>
> When I say crash, I mean really _crash_. IDLE stop responding, and I
> have to killall idle && killall python2.4 before I can res
I'm having trouble with this script. When I run it, it crashes IDLE...
which is no fun. :(
I'm running Ubuntu 6.06 w/ python 2.4
When I say crash, I mean really _crash_. IDLE stop responding, and I
have to killall idle && killall python2.4 before I can restart it (cause
python2.4 keeps the TCP
