Showing content from http://mail.python.org/pipermail/python-dev/attachments/20130504/1192c78f/attachment.html below:
<div dir="ltr">On 4 May 2013 15:20, Vinay Sajip <span dir="ltr"><<a href="mailto:vinay_sajip@yahoo.co.uk" target="_blank">vinay_sajip@yahoo.co.uk</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">Paul Moore <p.f.moore <at> <a href="http://gmail.com" target="_blank">gmail.com</a>> writes:<br>
<br>
> This will mean that scripts written with #!/usr/bin/env python will<br>
> behave the same on Unix and Windows in the presence of activated<br>
> virtualenvs.<br>
<br>
</div>Overall I think it's the right result. There's one other compatibility<br>
clarification: at the moment, as allowed by the PEP, you can have launcher<br>
flags in a line that starts with #!/usr/bin/env python, for example<br>
<br>
#!/usr/bin/env python3.2-32 -u<br>
<br>
In such a case the launcher would use the 3.2-32 suffix to indicate that<br>
32-bit Python 3.2 is wanted, and pass the -u to the launched executable. I<br>
assume that this behaviour should continue, and the Posix-compatible behaviour<br>
being proposed should only apply for lines that contain<br>
<br>
"#!/usr/bin/env python"<br>
<br>
followed by whitespace.<br></blockquote><div><br></div><div style>That sounds reasonable - I've never used the ability to add flags, but I agree that as there's no equivalent in POSIX, there's no reason to change the current behaviour in that case.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Also, since we're making a backwards incompatible change, do people feel that<br>
it needs to be switched on only in the presence of e.g. an environment variable<br>
such as PYLAUNCH_SEARCHPATH, or should we just change the default behaviour<br>
now and risk breaking user scripts which may rely on the current behaviour?<br></blockquote><div> </div><div style>Personally, I'd say make it unconditional - the current behaviour is unlikely to ever be what people actually *want*.</div>
<div style><br></div><div style>But if the consensus is to make it conditional, could we have a flag in py.ini rather than an environment variable? That would be more consistent with normal Windows practice.</div><div style>
<br></div><div style>Paul.</div><div style><br></div><div style>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.</div>
<div> </div></div><br></div></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4