<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#330033">
On 7/21/2011 8:20 AM, Michael Foord wrote:
<blockquote cite="mid:4E2843A7.4090502@voidspace.org.uk" type="cite">On
21/07/2011 15:43, Paul Moore wrote:
<br>
<blockquote type="cite" style="color: #000000;">On 21 July 2011
09:13, Glenn Linderman<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:v+python@g.nevcal.com"><v+python@g.nevcal.com></a>
wrote:
<br>
<blockquote type="cite" style="color: #000000;">Certainly when
the launcher is invoked via an association, this would
<br>
be the case. However, when the launcher is invoked via the
command
<br>
line, then the unqualified name is passed through. To be
useful from
<br>
the command line, the launcher should walk the PATH to find
the .py file.
<br>
</blockquote>
It's equally as arguable (and would match my expectations much
more
<br>
closely) that "py a_file.py" should do whatever "python
a_file.py"
<br>
would do. So path search in that context would only be
reasonable if
<br>
it were a Python feature rather than a feature of the launcher.
<br>
<br>
This is what the launcher currently does (so I guess it's not
<br>
surprising that I'm happy with the current behaviour).
<br>
<br>
I can see the benefits of path search, but I'd want it to be a
Python
<br>
feature (and hence inherited "for free" by the launcher) and not
a
<br>
launcher-only one.
<br>
</blockquote>
<br>
What he said ^^. (+1)
<br>
<br>
py launcher and python binaries behaving differently in this
regard would be a recipe for confusion and hard to debug problems.
</blockquote>
<br>
I see the point. Although the incremental benefit is higher to
Windows users, and although we are creating a Windows-only piece of
code that could be the vehicle for adding the functionality, it
would be beneficial for all platforms, and a common implementation
would serve that need better.<br>
</body>
</html>