Michael; <br> IIRC you are at pycon. (I am at the wrong end of America and Mark is at the wrong end of Earth. I couldn't make it.)<br> Can you create/find a bof session to hash out a "standard" shebang? It should be something good enough that 2to3 could have a fixer for it. <br>
--<br>[ reminder for the day:<br>Now is better than never.]<br><br>Mark:<br> Were you thinking part of the pywin32 distribution, or CPython itself? Either way we should have a compatible/identical tool installed with IronPython. The thing should be Frankensteinian enough that I can have it "cling" to my favorite distribution even when I install several others beside it. (Perhaps an environment variable or .python file?)<br>
--<br><br><div class="gmail_quote">Both/Group:<br> What about Jython? I have been using Jython 2.5 lately (not my fault -- a college class is making me learn Java after avoiding it for 20+ years -- but I installed the Jython support in NetBeans, too) and discover that they are having similar problems with how to crank up a Jython script from the command line. The "java -jar ..." string is nasty. This starter program could be a triple solution. Too much?<br>
--<br>Vernon<br><br>P.S. -- and when I double-click on a file named "setup.py" automatically add "install" to the generated command line.<br><br> Tue, Mar 15, 2011 at 8:28 AM, Michael Foord <span dir="ltr"><<a href="mailto:fuzzyman@voidspace.org.uk">fuzzyman@voidspace.org.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"><div class="im">
On 15/03/2011 07:18, Vernon Cole wrote:
<blockquote type="cite">
<p>#!/usr/bin/ipy3</p>
<p>A shebang on the first line is the usual way of specifying
which scripting engine to use on a posix system. If
introspection were to be used to select between python versions,
that would be the most obvious way to do it.</p>
<p>Windows (tm) prefers to use filename extensions, which is why
.pyw is used to specify a GUI program. The command shell does
not open the file to see what's inside AFAIK. </p>
<p>It was suggested in the past that .ipy might be used to
specify IronPython programs. If that idea were carried to its
logical end, one would use .ipy3w to specify an IronPython 3.x
GUI script. That is a bit frightening.</p>
<p>What about the idea of a semi-standard python dispatch program
which lives on the search path, introspects the script, and
calls the appropriate engine? Perhaps it could even manage to
capture tracebacks sent to stderr when a script dies?<br>
</p>
</blockquote>
<br></div>
There has been a long discussion recently on Python-dev [1]
suggesting the creation of exactly such a launcher program for
Python on Windows. Mark Hammond (copied) said he would implement it.
Including IronPython support is a fine idea.<br>
<br>
All the best,<br>
<br>
Michael<br></div></blockquote></div><br>