On 13 February 2015 at 07:02, Nick Coghlan wrote:
> Procedurally, since it's a Windows specific change, and assuming Guido
> doesn't want to pronounce on this one himself, perhaps Steve Dower
> would be an appropriate BDFL-Delegate?
The PEP is now up to date and the patch is on the tracker at
htt
On 14 Feb 2015 07:31, "Paul Moore" wrote:
>
> (By the way, on a procedural note, how do I update a PEP? Do I just
> send an updated version to p...@python.org, or is there a better way?)
If you're happy to handle the PEP editor responsibilities described in PEP
1 yourself, you can also ask for co
On 12 February 2015 at 19:44, Paul Moore wrote:
> Impact on Script Launching
> ==
Now that I'm looking into the details of the code for the launcher,
I've noticed that a shebang line of "#!/usr/bin/env python" will first
of all search PATH for a python executable, before f
On 13 February 2015 at 05:47, Ethan Furman wrote:
> Looks well thought-out.
>
> +1
I don't see any holes in the proposed behaviour either, so +1 from me.
Procedurally, since it's a Windows specific change, and assuming Guido
doesn't want to pronounce on this one himself, perhaps Steve Dower
woul
Looks well thought-out.
+1
--
~Ethan~
signature.asc
Description: OpenPGP digital signature
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/pyt
On 12 February 2015 at 14:46, Paul Moore wrote:
> If py.exe detected when the environment variable VIRTUAL_ENV was set,
> and used that virtualenv as the default Python rather than the
> "system" python it normally used, this would be perfect.
>
> I think I'll write a PEP for this. Do people think
