> From: Paul Moore
>Did you get a chance to have a look at this? I didn't manage to create a pull
>request against your copy of pylauncher as my repo
> is a fork of the pypa one - I'm not sure if that's a limitation of bitbucket
> or if I just don't know how to do it... I've created a pull requ
On 5 May 2013 18:10, Paul Moore wrote:
>
> On 4 May 2013 16:42, Vinay Sajip wrote:
>
>> I've taken a quick look at it, but I probably won't be able to make any
>> changes until the near the end of the coming week. Feel free to have a go;
>>
>
> OK, I have a patch against the standalone pylaunche
On 4 May 2013 16:42, Vinay Sajip wrote:
> I've taken a quick look at it, but I probably won't be able to make any
> changes until the near the end of the coming week. Feel free to have a go;
>
OK, I have a patch against the standalone pylauncher repo at
https://bitbucket.org/pmoore/pylauncher. I
Paul Moore gmail.com> writes:
> PS Vinay - from this post, I assume you're already looking at this
> code? I was considering trying to put together a patch, but I don't want to
> duplicate effort if you're working on it.
I've taken a quick look at it, but I probably won't be able to make any
cha
On 4 May 2013 15:20, Vinay Sajip wrote:
> Paul Moore gmail.com> writes:
>
> > This will mean that scripts written with #!/usr/bin/env python will
> > behave the same on Unix and Windows in the presence of activated
> > virtualenvs.
>
> Overall I think it's the right result. There's one other com
Paul Moore gmail.com> writes:
> This will mean that scripts written with #!/usr/bin/env python will
> behave the same on Unix and Windows in the presence of activated
> virtualenvs.
Overall I think it's the right result. There's one other compatibility
clarification: at the moment, as allowed by
On Sat, May 4, 2013 at 12:18 PM, Brian Curtin wrote:
> On Fri, May 3, 2013 at 3:23 PM, Paul Moore wrote:
>> I would propose that the behaviour of the launcher on Windows should be
>> changed when it encounters specifically the hashbang line #!/usr/bin/env
>> python. In that case, it should search
On Fri, May 3, 2013 at 3:23 PM, Paul Moore wrote:
> I would propose that the behaviour of the launcher on Windows should be
> changed when it encounters specifically the hashbang line #!/usr/bin/env
> python. In that case, it should search PATH for a copy of python.exe, and if
> it finds one, use
While reviewing the behaviour of Vinay's "distil" installer tool (see
distutils-sig for details, but it's not relevant here) I have found what I
think is a flaw in the behaviour of the py.exe launcher for Windows.
To recap for people unfamiliar with the launcher, it emulates #! line
interpretation
