[issue2584] numeric overflow in IDLE

Changes by Kurt B. Kaiser <[EMAIL PROTECTED]>: -- resolution: -> wont fix status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue2584] numeric overflow in IDLE

Tim Wilcoxson <[EMAIL PROTECTED]> added the comment: I guess my only reply isfair enough. heh. On Thu, May 22, 2008 at 1:07 PM, Kurt B. Kaiser <[EMAIL PROTECTED]> wrote: > > Kurt B. Kaiser <[EMAIL PROTECTED]> added the comment: > > When this is running, what happens if you hit Control-c a

[issue2584] numeric overflow in IDLE

Kurt B. Kaiser <[EMAIL PROTECTED]> added the comment: BTW, instead of a reboot, use Task Manager (or whatever they needlessly renamed it to on Vista :) to kill all python processes. That should free up your machine. __ Tracker <[EMAIL PROTECTED]>

[issue2584] numeric overflow in IDLE

Kurt B. Kaiser <[EMAIL PROTECTED]> added the comment: When this is running, what happens if you hit Control-c a few times, especially in the first few seconds? Does it abort with a KeyboardInterrupt? Does it stop responding to Control-c after the window fills up? Note that IDLE slows down wh

[issue2584] numeric overflow in IDLE

Changes by Kurt B. Kaiser <[EMAIL PROTECTED]>: -- assignee: -> kbk nosy: +kbk priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python

[issue2584] numeric overflow in IDLE

Tim Wilcoxson <[EMAIL PROTECTED]> added the comment: not a nick aye? lol. I am new cant you tell. And when i ran the script nothing could be closed. And, yes, I realize it could be a memory exhaustion issue with windows. windows is notorious for crappy resource handling. However, my concern came

[issue2584] numeric overflow in IDLE

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: So let's it interpret this way: range(1, 3) consumes more and more memory, and causes the system to hang. When python.exe is in a console, you have the ability to close the window and kill the process. When using Idle, the interp

[issue2584] numeric overflow in IDLE

Tim Wilcoxson <[EMAIL PROTECTED]> added the comment: msg65177, i did try to close cmd. thats why it closed. i wasnt clear enough. my apologies. it merely lags in command line in gives a memory error. in IDLE, it wont respond, and it gives a logon process erorr in windows if you try to view the s

[issue2584] numeric overflow in IDLE

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: I wonder why do you suspect a numeric overflow. It may very well be that the system needs more time to become responsive, when the script is run by Idle. Idle actually spawns another python process to execute commands. > then the cmd p

[issue2584] numeric overflow in IDLE

New submission from Tim Wilcoxson <[EMAIL PROTECTED]>: According to the documentation there is not suppose to be numeric overflow in python 2.5. However If you run a for loop with the range(1, 3)a couple of times (for me 2 or 3 times worked) in the IDLE (1.2.2)GUI . It will cause wha