On Sat, Sep 20, 2014 at 5:43 AM, Terry Reedy wrote:
> On 9/18/2014 10:51 PM, Chris Angelico wrote:
>>
>> On Fri, Sep 19, 2014 at 5:05 AM, Terry Reedy wrote:
>>>
>>> A couple more questions; after you run the file once, is there a warning
>>> above the first >>> prompt? If, after the program stop
On 9/18/2014 10:51 PM, Chris Angelico wrote:
On Fri, Sep 19, 2014 at 5:05 AM, Terry Reedy wrote:
A couple more questions; after you run the file once, is there a warning
above the first >>> prompt? If, after the program stop and you see a second
prompt and run
import sys; len(sys.modules), 'a
On Fri, Sep 19, 2014 at 5:05 AM, Terry Reedy wrote:
> A couple more questions; after you run the file once, is there a warning
> above the first >>> prompt? If, after the program stop and you see a second
prompt and run
import sys; len(sys.modules), 'array' in sys.modules
> what is the
On Thu, 18 Sep 2014 15:05:53 -0400, Terry Reedy
wrote:
>On 9/18/2014 11:24 AM, Seymore4Head wrote:
>> On Wed, 17 Sep 2014 23:50:56 -0400, Terry Reedy
>> wrote:
>
>>> My question was "How do you start Idle?"
>>> (I can make a difference.)
>>
>> The way I start IDLE is to go to my programs folder
On 9/18/2014 11:24 AM, Seymore4Head wrote:
On Wed, 17 Sep 2014 23:50:56 -0400, Terry Reedy
wrote:
My question was "How do you start Idle?"
(I can make a difference.)
The way I start IDLE is to go to my programs folder and right click on
file.py in the directory and select "edit with IDLE".
de in idlelib/PyShell.py, about 825.
>>>
>>> def display_executing_dialog(self):
>>> tkMessageBox.showerror(
>>> "Already executing",
>>> "The Python Shell window is already executing a command; &quo
(self):
tkMessageBox.showerror(
"Already executing",
"The Python Shell window is already executing a command; "
"please wait until it is finished.",
master=self.tkconsole.text)
This function is only called here (about line 735)
def ru
thout making any changes I
>>>> just hit f5 to rerun the program.
>>>> Sometimes I get the error "the python shell window is already
>>>> executing a command" and sometimes not.
>
>You left out an important part of the error message ""please
this
one again. I could run the program by pushing f5. The first couple
of times it would run again by switching back to IDLE and pressing f5,
but after the second or third time, it gives an error that the python
shell window is already executing a command.
If I make a change to the program, li
o is click on the IDLE window and without making any changes I
>> just hit f5 to rerun the program.
>
>Do you mean click on the Idle editor window?
>
>> Sometimes I get the error "the python shell window is already
>> executing a command" and sometimes not.
you mean click on the Idle editor window?
Sometimes I get the error "the python shell window is already
executing a command" and sometimes not.
I am using XP and Python 3.4.1.
Is there a way to rerun a program without getting this error?
Normally, hitting f5 kills the previous proces
I have googled for a solution to this problem. None I have tried
worked.
I have a very short program that runs for a count of 20 and ends.
What I do is click on the IDLE window and without making any changes I
just hit f5 to rerun the program.
Sometimes I get the error "the python shell w
> find the errand CMD prompt and move it.
errand -> errant
--
http://mail.python.org/mailman/listinfo/python-list
Jay wrote:
> Is their any way of setting wear the Python Shell window appears on the
> screen when I run my program?
>
> I am testing a full screen program with no Window Frame on a comp with
> 2 monitors and I have to keep pressing the Key to bring the
> Shell to the front
Is their any way of setting wear the Python Shell window appears on the
screen when I run my program?
I am testing a full screen program with no Window Frame on a comp with
2 monitors and I have to keep pressing the Key to bring the
Shell to the front and then moving it manually to the other
15 matches
Mail list logo