You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In principle one can use the reinitialize command (Run, Python Engine,
Reinitialize) to interrupt the interpreter but this not only stops execution
but resets the interpreter entirely. That means it forgets everything including
the current directory, code loaded, variable asignments and so on.
For testing purposes it is useful to build up an environment in the
interpreter and test individual functions. If for some reason the
interpreter hangs (gets in an infinite loop, test data is too big to process
and one gets bored waiting...) it is a nuisance to lose context when resetting
the interpreter.
Original issue reported on code.google.com by patric...@gmx.de on 6 Mar 2012 at 7:39
The text was updated successfully, but these errors were encountered:
I managed to get a way to raise a Keyboard interrupt to at the remote
interpreter utilizing Windows calls without incurring overheads.
So Reinitializing the Remote engine is no longer necessary for stopping an
infinitely looping script. You just need to press the Abort button.
Original comment by pyscripter on 10 Mar 2012 at 12:11
Where/what is this "Abort" button of which you speak? When pyscripter hangs and I click anywhere on the window, it greys out and I can't do anything other than kill the whole thing.
Original issue reported on code.google.com by
patric...@gmx.de
on 6 Mar 2012 at 7:39The text was updated successfully, but these errors were encountered: