On Monday, Apr 23rd 2007 at 17:31 +0100, quoth Michael Hoffman:
=>Steven W. Orr wrote:
=>> On Saturday, Apr 21st 2007 at 19:18 +0100, quoth Michael Hoffman:
=>>
=>> =>Chris Lasher wrote:
=>> =>> Should a Python module not intended to be executed have shebang/
=>> =>> hashbang (e.g., "#!/usr/bin/e
Michael Hoffman wrote:
> Steven W. Orr wrote:
>> On Saturday, Apr 21st 2007 at 19:18 +0100, quoth Michael Hoffman:
>>
>> =>Chris Lasher wrote:
>> =>> Should a Python module not intended to be executed have shebang/
>> =>> hashbang (e.g., "#!/usr/bin/env python") or not? I'm used to having a
>> =>>
Steven W. Orr wrote:
> On Saturday, Apr 21st 2007 at 19:18 +0100, quoth Michael Hoffman:
>
> =>Chris Lasher wrote:
> =>> Should a Python module not intended to be executed have shebang/
> =>> hashbang (e.g., "#!/usr/bin/env python") or not? I'm used to having a
> =>> shebang in every .py file but
On Saturday, Apr 21st 2007 at 19:18 +0100, quoth Michael Hoffman:
=>Chris Lasher wrote:
=>> Should a Python module not intended to be executed have shebang/
=>> hashbang (e.g., "#!/usr/bin/env python") or not? I'm used to having a
=>> shebang in every .py file but I recently heard someone argue th
Chris Lasher wrote:
> Should a Python module not intended to be executed have shebang/
> hashbang (e.g., "#!/usr/bin/env python") or not? I'm used to having a
> shebang in every .py file but I recently heard someone argue that
> shebangs were only appropriate for Python code intended to be
> execut
Jorgen Grahn a écrit :
> On Fri, 13 Apr 2007 22:46:03 +0200, Bruno Desthuilliers <[EMAIL PROTECTED]>
> wrote:
>
>>Jorgen Grahn a écrit :
>
(snip)
>
>>More seriously, and as far as I'm concerned, when I want to make a
>>python script (by opposition to a python 'module') available as a unix
>>c
On Fri, 13 Apr 2007 22:46:03 +0200, Bruno Desthuilliers <[EMAIL PROTECTED]>
wrote:
> Jorgen Grahn a écrit :
...
>> If you distribute a
>> Python program to Unix users in that form, they may not want to know
>> or care which language it's written in. Especially if you decide, a
>> few releases late
Jorgen Grahn a écrit :
> On Thu, 12 Apr 2007 00:24:12 +0200, Bruno Desthuilliers <[EMAIL PROTECTED]>
> wrote:
>
>>Chris Lasher a écrit :
>>
>>>Should a Python module not intended to be executed have shebang/
>>>hashbang (e.g., "#!/usr/bin/env python") or not?
>>
>>The shebang is only useful for f
On 13 Apr 2007 10:54:18 GMT, Jorgen Grahn <[EMAIL PROTECTED]> wrote:
> On Thu, 12 Apr 2007 00:24:12 +0200, Bruno Desthuilliers <[EMAIL PROTECTED]>
> wrote:
>> Chris Lasher a écrit :
>>> Should a Python module not intended to be executed have shebang/
>>> hashbang (e.g., "#!/usr/bin/env python") or
On Thu, 12 Apr 2007 00:24:12 +0200, Bruno Desthuilliers <[EMAIL PROTECTED]>
wrote:
> Chris Lasher a écrit :
>> Should a Python module not intended to be executed have shebang/
>> hashbang (e.g., "#!/usr/bin/env python") or not?
>
> The shebang is only useful for files that you want to make directl
"Chris Lasher" <[EMAIL PROTECTED]> writes:
> I recently heard someone argue that shebangs were only appropriate
> for Python code intended to be executable (i.e., run from the
> command line).
Since that's the purpose of putting in a shebang line, that's what I'd
argue also; specifically:
- Mo
Chris Lasher a écrit :
> Should a Python module not intended to be executed have shebang/
> hashbang (e.g., "#!/usr/bin/env python") or not?
The shebang is only useful for files that you want to make directly
executable on a *n*x system. They are useless on Windows, and not
technically required
On Apr 11, 5:29 pm, "Chris Lasher" <[EMAIL PROTECTED]> wrote:
> Should a Python module not intended to be executed have shebang/
> hashbang (e.g., "#!/usr/bin/env python") or not? I'm used to having a
> shebang in every .py file but I recently heard someone argue that
> shebangs were only appropria
Should a Python module not intended to be executed have shebang/
hashbang (e.g., "#!/usr/bin/env python") or not? I'm used to having a
shebang in every .py file but I recently heard someone argue that
shebangs were only appropriate for Python code intended to be
executable (i.e., run from the comma
14 matches
Mail list logo