I'm kind of -1 on changing Python executable name. It would make sense for different major versions, where there are known incompatibilities, so python2-python3 would make sense but python31 python32 not that much...<div>
<br></div><div>If my team is using Python and it gets pre-installed with other dev-tools, do I need to let everyone know they must call python<b>31</b>? And if we upgrade, make sure everyone knows they should now call python<b>32</b>? What if we have scripts that call python? Make sure we update all of them whenever minor version is changed?</div>
<div><br></div><div>The way I look at it, most people have only one version of Python installed at one time and it's just extra burden to make them remember major+minor version number they have. If you actually install multiple versions, you do that for a reason and, since you know what you're doing, you would rather remember to pass correct -v argument to py than users who <i>just want to use Python</i>.</div>
<div><br></div><div>Thank you,</div><div>Vlad<br><br><div class="gmail_quote">On Thu, Jul 21, 2011 at 12:42 PM, Terry Reedy <span dir="ltr"><<a href="mailto:tjreedy@udel.edu">tjreedy@udel.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 7/20/2011 7:55 PM, Mark Hammond wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 21/07/2011 4:38 AM, Terry Reedy wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Many installers first make an organization directory and then an app<br>
directory within that. This annoys me sometimes when they only have one<br>
app to ever install, but is useful when there might really be multiple<br>
directories, as in our case. (Ditto for start menu entries.) This is<br>
what python should have done a decade ago.<br>
</blockquote></blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I disagree. If we followed that advice we would also be in "\Program<br>
Files".<br>
</blockquote>
<br></div>
That is not what I suggested. I said let the use pick.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have no problem with multiple Python versions installed<br>
directly off the root, especially given most users probably have a very<br>
small number of such installations. I think Python being a developer<br>
tool rather than a user app is a reasonable justification for that (and<br>
the justification used when the existing scheme was decided)<br>
</blockquote>
<br></div>
I put the multiple installations and several other directories into /programs. On my next machine, on order, I will use /devel.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> The two proposals<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
overlap but are not mutually exclusive. For future pythons, 'python33'<br>
is easier to remember and type than 'py -v 3.3' or whatever the proposed<br>
encantation is.<br>
</blockquote>
<br>
'py -3.3' - less chars to type than 'python33' and with no need to have<br>
every Python directory on your PATH.<br>
</blockquote>
<br></div>
My proposal, as I clearly said, was for EXACTLY ONE directory to be added to PATH. In spite of Microsoft making is damned difficult for users to edit PATH, (and deleted programs not deleting their entries) I added 'C:/programs;'. I copied python32/python as py32 and python27/python as py27. Those are even fewer characters to type (4 versus 7). Now I can click a 'Command Prompt' icon and enter 'py32 -m test.regrtest' and it works without cd-ing to /programs/python32. Of course, I will have to re-copy with every install, which is why I would like something like this as part of installs.<div class="im">
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
IMO it is also simple enough that<br>
people will remember it fairly easily.<br>
</blockquote>
<br></div>
py32 is even easier to remember.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Also, the launcher supports the ability to select either the 32 or 64bit<br>
implementation - so maybe 'python33.exe' isn't really good enough and<br>
should reflect the bittedness?<br>
</blockquote>
<br></div>
Like py32-6? If I install both Pythons on my new 64 bit machine, I will think about it, though I have no need for both now.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
A python directory also gives a sensible (though optional) place to put<br>
other interpreters and even python-based apps. The launcher does not.<br>
</blockquote>
<br>
What other interpreters? IMO it doesn't make sense to have IronPython,<br>
jython etc be installed there. Ditto for apps - especially given most<br>
apps tend to be tied to a subset of all possible Python versions.<br>
</blockquote>
<br></div>
If I install pypy, /programs is exactly where I would put it until I somehow discovered that to be a problem. Its startup could be copied as pp26 or something.<br>
<br>
<br>
My idea may be not so good for general use, even though is now solves my problems, but please criticize what I said, allowing for obvious modifications like py32 instead of python32, and not a strawman that is wildly different.<br>
<font color="#888888">
<br>
-- <br>
Terry Jan Reedy</font><div><div></div><div class="h5"><br>
<br>
______________________________<u></u>_________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org" target="_blank">Python-Dev@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/python-dev" target="_blank">http://mail.python.org/<u></u>mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="http://mail.python.org/mailman/options/python-dev/riscutiavlad%40gmail.com" target="_blank">http://mail.python.org/<u></u>mailman/options/python-dev/<u></u>riscutiavlad%40gmail.com</a><br>
</div></div></blockquote></div><br></div>