On Nov 11, 2014, at 03:52 PM, Neal McBurnett wrote:
>I should have clarified my point better. Scott's message recommended putting
>python, rather than python2 in shebangs, since it works in more distros.
>That seems to be In contrast with PEP 394, which says to use python2 rather
>than python, un
On Tuesday, November 11, 2014 15:52:22 Neal McBurnett wrote:
> On Tue, Nov 11, 2014 at 05:19:38PM -0500, Barry Warsaw wrote:
> > On Nov 11, 2014, at 11:48 AM, Neal McBurnett wrote:
> > >I'm glad that python2 is in Debian and Ubuntu (do you know offhand which
> > >releases?). Which distros is it st
On Tue, Nov 11, 2014 at 05:19:38PM -0500, Barry Warsaw wrote:
> On Nov 11, 2014, at 11:48 AM, Neal McBurnett wrote:
>
> >I'm glad that python2 is in Debian and Ubuntu (do you know offhand which
> >releases?). Which distros is it still not supported in? Are they likely to
> >catch up?
>
> Sorry,
On Nov 11, 2014, at 11:48 AM, Neal McBurnett wrote:
>I'm glad that python2 is in Debian and Ubuntu (do you know offhand which
>releases?). Which distros is it still not supported in? Are they likely to
>catch up?
Sorry, I don't know off-hand.
>Do you see a path to a world where compliance with
On Tue, Nov 11, 2014 at 01:35:09PM -0500, Scott Kitterman wrote:
> On Tuesday, November 11, 2014 13:04:38 Rodney Dawes wrote:
> > On Tue, 2014-11-11 at 18:02 +0100, GatoLoko wrote:
> > > Since different distributions and unix systems may have different paths,
> > > you may want to use the env utili
On Tuesday, November 11, 2014 13:04:38 Rodney Dawes wrote:
> On Tue, 2014-11-11 at 18:02 +0100, GatoLoko wrote:
> > Since different distributions and unix systems may have different paths,
> > you may want to use the env utility in a shebang like "#!/usr/bin/env
> > python2".
>
> Using /usr/bin/en
On Nov 11, 2014, at 01:04 PM, Rodney Dawes wrote:
>Using /usr/bin/env will cause problems in certain conditions, such as
>when running under a virtualenv and other such environments.
The general recommendation is that /usr/bin/env is a good shebang to use when
your package is under development, b
On Tue, 2014-11-11 at 18:02 +0100, GatoLoko wrote:
> Since different distributions and unix systems may have different paths,
> you may want to use the env utility in a shebang like "#!/usr/bin/env
> python2".
Using /usr/bin/env will cause problems in certain conditions, such as
when running und
El 23/10/14 a las 00:31, vova escribió:
PEP 394 and 397 suggest a simplified form `#!python2` — it works on
Windows 7 and 8 just fine.
None of those PEPs suggest the use of a line like that. PEP 397 is about
a launcher, and that launcher could support that kind of line.
Windows doesn't know
PEP 394 and 397 suggest a simplified form `#!python2` — it works on Windows
7 and 8 just fine.
But Ubuntu 14.04 claims ‘no such file’, though python2 is in PATH.
I googled that issue and found only similar issue with DOS line endings, but
I’m sure that mine script contains Unix ones.
So I gue
10 matches
Mail list logo
