On Sat, 16 Feb 2013 21:27:28 +1000
Nick Coghlan wrote:
> On Sat, Feb 16, 2013 at 9:17 PM, Nick Coghlan wrote:
> > Since Antoine and Stephen have pointed out my only non-cosmetic
> > concern was an error on my part, I am accepting the PEP. I'll update
> > the peps repo (including the cosmetic fix
On Sat, Feb 16, 2013 at 9:17 PM, Nick Coghlan wrote:
> Since Antoine and Stephen have pointed out my only non-cosmetic
> concern was an error on my part, I am accepting the PEP. I'll update
> the peps repo (including the cosmetic fixes) in a moment.
And done: http://hg.python.org/peps/rev/d272d7a
Since Antoine and Stephen have pointed out my only non-cosmetic
concern was an error on my part, I am accepting the PEP. I'll update
the peps repo (including the cosmetic fixes) in a moment.
Regards,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
Nick Coghlan writes:
> For compatibility with file encoding declarations, I believe this
> needs to be relaxed to starting with '#!python' in the source file
> encoding, rather than strictly b'#!python' (which will only be the
> case for ASCII compatible encodings).
In any PEP-263-compatible
On Sat, Feb 16, 2013 at 8:12 PM, Antoine Pitrou wrote:
> On Sat, 16 Feb 2013 19:18:22 +1000
> Nick Coghlan wrote:
> I may be wrong, but I am not aware that Python is able to read encoding
> declarations in a non-ASCII compatible encoding :-)
>
> Also, given the shebang line is for use by the OS,
On Sat, 16 Feb 2013 11:12:49 +0100
Antoine Pitrou wrote:
> On Sat, 16 Feb 2013 19:18:22 +1000
> Nick Coghlan wrote:
> > On Sat, Feb 16, 2013 at 2:21 PM, Daniel Holth wrote:
> > > #. Python scripts must appear in ``scripts`` and begin with exactly
> > >``b'#!python'`` in order to enjoy scrip
On Sat, 16 Feb 2013 19:18:22 +1000
Nick Coghlan wrote:
> On Sat, Feb 16, 2013 at 2:21 PM, Daniel Holth wrote:
> > #. Python scripts must appear in ``scripts`` and begin with exactly
> >``b'#!python'`` in order to enjoy script wrapper generation and
> >``#!python`` rewriting at install tim
On Sat, Feb 16, 2013 at 2:21 PM, Daniel Holth wrote:
> #. Python scripts must appear in ``scripts`` and begin with exactly
>``b'#!python'`` in order to enjoy script wrapper generation and
>``#!python`` rewriting at install time. They may have any or no
>extension.
For compatibility w
