; Sent: Thursday, April 05, 2007 4:28 AM
> To: tutor@python.org
> Subject: Re: [Tutor] windows and python and shebangs, oh my!
>
> "Kirk Bailey" <[EMAIL PROTECTED]> wrote
>
>> OK, in a script, we include a special statement telling the shell
>> where to go
windows registry. The setting is
ScriptInterpreterSource registry
-jdc
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Alan Gauld
Sent: Thursday, April 05, 2007 4:28 AM
To: tutor@python.org
Subject: Re: [Tutor] windows and python and shebangs, oh my
"Kirk Bailey" <[EMAIL PROTECTED]> wrote
> OK, in a script, we include a special statement telling the shell
> where
> to go find the interpeter. This is the first line of the script, and
> is
> a dpecial sort of comment, called informally the shebang.
Yes, but it is not a Python feature it is a
Kirk Bailey wrote:
> OK, in a script, we include a special statement telling the shell where
> to go find the interpeter. This is the first line of the script, and is
> a dpecial sort of comment, called informally the shebang. it looks like
> this:
> #!C:\path\interpeterprogramname
>
> In window
On 05/04/07, Kirk Bailey <[EMAIL PROTECTED]> wrote:
> So work with me, windows Pythonistas. CAN I rely on windows definitely
> and reliably having .py files associated with the windows python
> interpreter, so the script does not need a shebang declaration? Can I
> skip this part of the configure/i
OK, in a script, we include a special statement telling the shell where
to go find the interpeter. This is the first line of the script, and is
a dpecial sort of comment, called informally the shebang. it looks like
this:
#!C:\path\interpeterprogramname
In windows, this is for the current editi
