se. As someone mentioned from this list, at least it'll be code
>> that is easier to read for a newbie like myself.
>>
>> (Hope that didn't confuse or cause unnecessary headaches...)
>>
>> Sara
>>
>> - Original Message
>> From:
Message
> From: Luke Paireepinart <[EMAIL PROTECTED]>
> To: Tiger12506 <[EMAIL PROTECTED]>
> Cc: tutor@python.org
> Sent: Monday, July 16, 2007 7:00:53 PM
> Subject: Re: [Tutor] interpreter restarts
>
> Tiger12506 wrote:
> >> But there's an exception to
Luke Paireepinart wrote:
> Tiger12506 wrote:
>>> As you will notice, there are some parameters there at the end.
>>> the -n is the one you're interested in .
>>> -n means no subprocess.
>>>
>> Yes. Yes. That is what I'm interested in.
>> Sigh. I know Windows very well for my background. The co
Tiger12506 wrote:
> Hmmm. You should read closer ;-)
>
Heh. You're right, I didn't read your whole message. I just skimmed it :P
>
>> It sounds like python_icon.exe is a fake executable that just contains the
>> icon for python programs...
>> hence the name.
>>
>
> Perhaps. If that's
Hmmm. You should read closer ;-)
> It sounds like python_icon.exe is a fake executable that just contains the
> icon for python programs...
> hence the name.
Perhaps. If that's the case though, someone needs to talk to the guys who
design the setup file for python. It is an inefficient waste of
age
From: Luke Paireepinart <[EMAIL PROTECTED]>
To: Tiger12506 <[EMAIL PROTECTED]>
Cc: tutor@python.org
Sent: Monday, July 16, 2007 7:00:53 PM
Subject: Re: [Tutor] interpreter restarts
Tiger12506 wrote:
>> But there's an exception to that - if you right-click a file in Windoze
Tiger12506 wrote:
>> But there's an exception to that - if you right-click a file in Windoze
>> and 'edit' it,
>> IDLE won't open up its subprocess, and as such, it can't restart the
>> interpreter session because it's running in the same
>> process as IDLE, and to restart the interpreter would mea
> But there's an exception to that - if you right-click a file in Windoze
> and 'edit' it,
> IDLE won't open up its subprocess, and as such, it can't restart the
> interpreter session because it's running in the same
> process as IDLE, and to restart the interpreter would mean restarting
> IDLE.
>
Alan Gauld wrote:
> "elis aeris" <[EMAIL PROTECTED]> wrote
>
>
>> from a file, i click run from the IDLE interpreter
>>
>
> OK, Thats just normal IDLE behaviour. The Python shell
> restarts so your module doesn't pick up any junk lying
> around from the previous run.
>
But there's an
ohhh, you are the greatest :))
___
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
"Tiger12506" <[EMAIL PROTECTED]> wrote
> If you run an already saved file, the shell does not restart.
> I am curious why this occurs also.
It does it for me, I get a restart banner every time I run a file,
saved or not.
Alan G
___
Tutor maillist -
"elis aeris" <[EMAIL PROTECTED]> wrote
> from a file, i click run from the IDLE interpreter
OK, Thats just normal IDLE behaviour. The Python shell
restarts so your module doesn't pick up any junk lying
around from the previous run.
Alan G.
___
Tuto
Interesting... This is something very strange.
I've been able to reproduce the phenomenon that elis described.
Here's how to reproduce the error.
1) Open a new edit window in IDLE
2) type in code - do NOT save
3) Select Run Module from the Run menu
4) Save file when prompted
When the IDLE shell
from a file, i click run from the IDLE interpreter
On 7/14/07, elis aeris <[EMAIL PROTECTED]> wrote:
IDLE
On 7/14/07, Alan Gauld <[EMAIL PROTECTED]> wrote:
>
>
> "elis aeris" <[EMAIL PROTECTED]> wrote
>
> > why deos the interpreter restarts with this?
>
> Which interpreter?
> Command prompt py
IDLE
On 7/14/07, Alan Gauld <[EMAIL PROTECTED]> wrote:
"elis aeris" <[EMAIL PROTECTED]> wrote
> why deos the interpreter restarts with this?
Which interpreter?
Command prompt python? IDLE? PythonWin?
PyCrust?
And are you running them line by line manually
or is the code in a file?
> f = op
"elis aeris" <[EMAIL PROTECTED]> wrote
> why deos the interpreter restarts with this?
Which interpreter?
Command prompt python? IDLE? PythonWin?
PyCrust?
And are you running them line by line manually
or is the code in a file?
> f = open("data.ini","w")
>
> f.write("yeahppe")
>
> f.close()
On Sat, 14 Jul 2007, elis aeris wrote:
> why deos the interpreter restarts with this?
>
> f = open("data.ini","w")
>
> f.write("yeahppe")
>
> f.close()
Not sure. It certainly doesn't, for me.
>>> f = open("data.ini","w")
>>> f.write("yeahppe")
>>> f.close()
>>>
U:\>cat data.ini
yeahppe
_
17 matches
Mail list logo
