On Sun, Feb 22, 2015 at 1:10 AM, Dave Angel wrote:
> But you could always write your own py.exe, which interprets the shebang
> differently.
>
> Or run python.exe yourself, which as far as I know, pays no attention to
> shebang lines.
Or, my preferred solution: Fix the shebangs :) It's usually no
On 02/21/2015 06:05 AM, Gisle Vanem wrote:
Dave Angel wrote:
Finally, when py.exe starts, it reads that first (shebang) line, and
decides which python interpreter to actually use.
py.exe? Do you mean python.exe?
Reread my post, or read Mark's reply to yours. The job of py.exe or
pyw.exe i
On 21/02/2015 11:05, Gisle Vanem wrote:
Dave Angel wrote:
Finally, when py.exe starts, it reads that first (shebang) line, and
decides which python interpreter to actually use.
py.exe? Do you mean python.exe?
py.exe or pyw.exe come with the Python launcher on Windows and work out
which ve
Dave Angel wrote:
Finally, when py.exe starts, it reads that first (shebang) line, and decides
which python interpreter to actually use.
py.exe? Do you mean python.exe?
Is there a way to make python.exe ignore all Shebang lines
in all scripts? I had many generated .py-files with:
#!g:\Prog
On 20.02.2015 19:25, Ian Kelly wrote:
On Fri, Feb 20, 2015 at 8:16 AM, loial wrote:
On Friday, February 20, 2015 at 2:54:26 PM UTC, Ian wrote:
On Feb 20, 2015 7:46 AM, "loial" wrote:
On Linux we use
#!/usr/bin/env python
At the start of scripts to ensure that the python execut
On 20/02/2015 15:16, loial wrote:
On Friday, February 20, 2015 at 2:54:26 PM UTC, Ian wrote:
On Feb 20, 2015 7:46 AM, "loial" wrote:
On Linux we use
#!/usr/bin/env python
At the start of scripts to ensure that the python executable used is the one
defined in the PATH variable,
On Fri, Feb 20, 2015 at 8:16 AM, loial wrote:
> On Friday, February 20, 2015 at 2:54:26 PM UTC, Ian wrote:
>> On Feb 20, 2015 7:46 AM, "loial" wrote:
>>
>> >
>>
>> > On Linux we use
>>
>> > #!/usr/bin/env python
>>
>> >
>>
>> > At the start of scripts to ensure that the python executable used is
On Friday, February 20, 2015 at 2:54:26 PM UTC, Ian wrote:
> On Feb 20, 2015 7:46 AM, "loial" wrote:
>
> >
>
> > On Linux we use
>
> > #!/usr/bin/env python
>
> >
>
> > At the start of scripts to ensure that the python executable used is the
> > one defined in the PATH variable, rather than
On Feb 20, 2015 7:46 AM, "loial" wrote:
>
> On Linux we use
> #!/usr/bin/env python
>
> At the start of scripts to ensure that the python executable used is the
one defined in the PATH variable, rather than hardcoding a path to the
python executable.
>
> What is the equivalent functionality in Win
On 02/20/2015 09:43 AM, loial wrote:
On Linux we use
#!/usr/bin/env python
At the start of scripts to ensure that the python executable used is the one
defined in the PATH variable, rather than hardcoding a path to the python
executable.
What is the equivalent functionality in Windows?
Dep
On Linux we use
#!/usr/bin/env python
At the start of scripts to ensure that the python executable used is the one
defined in the PATH variable, rather than hardcoding a path to the python
executable.
What is the equivalent functionality in Windows?
--
https://mail.python.org/mailman/listinf
11 matches
Mail list logo
