> Okay. I've resolved this by standardising to the recommended shebang
> line on all Python programs in the package, and removing unused
> shebang lines from non-executable Python modules.
Thanks! But it seems that the "standard" way of write a shebang[1] is
#!/path/to/interpreter
without the sp
On 12-Jun-2008, Sandro Tosi wrote:
> On Thu, Jun 12, 2008 at 08:50, Ben Finney <[EMAIL PROTECTED]> wrote:
> > So I'd advise that the minimal change for this bug would be to
> > have a standard Debian shebang line of "#! /usr/bin/python".
>
> Fine, thanks for pointing it out.
>
> Now, since you h
On Thu, Jun 12, 2008 at 08:50, Ben Finney <[EMAIL PROTECTED]> wrote:
> It's true that one convention in the Python community is a shebang
> line of "#! /usr/bin/env python".
>
> However, the Debian Python Policy, ยง1.3.2
> specifically
> recommends against that practice.
>
>1.3.2. Interpreter L
On 12-Jun-2008, Sandro Tosi wrote:
> Hi Neil,
>
> > The conventional shebang line for python scripts is #!/usr/bin/env
> > python. However, I can see that reportbug might want to eliminate the
> > possibility of a non-standard python (eg from /usr/local) so just taking
> > the -S off is probably t
Hi Neil,
> The problem seems to be due to the use of python -S in the shebang line.
> The -S option disables 'import site' on initialization. If I edit
> /usr/bin/reportbug and remove the -S, the problem goes away.
>
> The conventional shebang line for python scripts is #!/usr/bin/env
> python. Ho
Package: reportbug
Followup-For: Bug #484534
The problem seems to be due to the use of python -S in the shebang line.
The -S option disables 'import site' on initialization. If I edit
/usr/bin/reportbug and remove the -S, the problem goes away.
The conventional shebang line for python scripts is
6 matches
Mail list logo
