<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 04/03/2011 17:45, Kerrick Staley wrote:
<blockquote
cite="mid:AANLkTim8f701W3qmyhYvUoWK9ECWtzTU8KsjiYTPT3vy@mail.gmail.com"
type="cite">
<div><font face="arial, sans-serif"><span style="border-collapse:
collapse;">> </span></font><span style="border-collapse:
collapse; font-family: arial,sans-serif; font-size: 13px;">Right,
but on Mac OS X we do put a "python3" on the path but not a
"python2". We also</span></div>
<div><span style="border-collapse: collapse; font-family:
arial,sans-serif; font-size: 13px;"></span><span
style="border-collapse: collapse; font-family:
arial,sans-serif; font-size: 13px;">> create "python2.x"
and "python3.x" variants.</span></div>
<div><span style="border-collapse: collapse; font-family:
arial,sans-serif; font-size: 13px;"><br>
</span></div>
<div><font face="arial, sans-serif"><span style="border-collapse:
collapse;">The PEP makes a recommendation for all *nix
platform, which includes Mac OS X. I was not aware that
Apple preinstalled Python on OS X, but it doesn't really
matter: Apple is the "distribution maintainer", and they
will be expected to follow the recommendations of this PEP.
Even if Apple is sluggish in getting this change pushed out,
it can be resolved on a per-system basis by the sysadmin.</span></font></div>
<div><font face="arial, sans-serif"><span style="border-collapse:
collapse;"><br>
</span></font></div>
</blockquote>
<br>
So there are three issues:<br>
<br>
* What Apple does with the system install - out of our control but
we can make recommendations<br>
* What `make install` does on Mac OS X<br>
* What the standard Mac OS X installer does<br>
<br>
The last two of these are in our control. If we actually make
changes to the build/install scripts of 2.7, rather than just
recommendations for distributions, then it would be nice to see the
changes in the installer as well as the build script. This would
ultimately be up to Ronald or Ned who do the Mac OS X work of
course.<br>
<br>
<blockquote
cite="mid:AANLkTim8f701W3qmyhYvUoWK9ECWtzTU8KsjiYTPT3vy@mail.gmail.com"
type="cite">
<div>
<font face="arial, sans-serif"><span style="border-collapse:
collapse;">> On Windows we only have a "python.exe" I
believe, but if the user does put their Python</span></font></div>
<div><span style="border-collapse: collapse; font-family:
arial,sans-serif; font-size: 13px;">> installs on the path
then we *could* usefully create "python2.exe" and
"python3.exe" for</span></div>
<div><span style="border-collapse: collapse; font-family:
arial,sans-serif; font-size: 13px;">> them. I don't see
that duplicating these binaries on the filesystem is an issue.
File</span></div>
<div><span style="border-collapse: collapse; font-family:
arial,sans-serif; font-size: 13px;">> associations is just
unsolvable on Windows, so it isn't something we can address or
should</span></div>
<div><span style="border-collapse: collapse; font-family:
arial,sans-serif; font-size: 13px;">> worry about.
(Actually a stub python.exe that looks at the shebang line and
then</span></div>
<div>
<span style="border-collapse: collapse; font-family:
arial,sans-serif; font-size: 13px;">> delegates to the
appropriate pythonX.Y.exe would be a possibility but I'm not</span></div>
<div><span style="border-collapse: collapse; font-family:
arial,sans-serif; font-size: 13px;">> volunteering to write
it.)</span><br>
<br>
</div>
<div>I like your idea for Windows, but it would take time to
implement this solution, and we won't be able to finalize the
solution for *nix as quickly if we also provide a provision for
Windows in this same PEP.</div>
</blockquote>
<br>
I don't think duplicating python.exe as python2.exe or python3.exe
would be very much work at all, if we decide it is a good thing.
Sure it doesn't resolve all the myriad problems of Python on Windows
but I don't think that is a good reason not to consider it. Up to
Martin on this one though and again depends if we just make
recommendations or actually change Python 2.7.<br>
<br>
All the best,<br>
<br>
Michael<br>
<br>
<blockquote
cite="mid:AANLkTim8f701W3qmyhYvUoWK9ECWtzTU8KsjiYTPT3vy@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>We should keep the use of the singular "they"; it's more
popular than the universal "he" (I intended the universal,
rather than gender-specific, meaning in the drafts of the PEP).</div>
<div><br>
</div>
<div>-Kerrick Staley</div>
<div><br>
</div>
<div>
<div class="gmail_quote">On Fri, Mar 4, 2011 at 9:50 AM, Ronald
Oussoren <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ronaldoussoren@mac.com" target="_blank">ronaldoussoren@mac.com</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>
<div>
<div><br>
<br>
On 04 Mar, 2011,at 02:21 PM, Nick Coghlan <<a
moz-do-not-send="true"
href="mailto:ncoghlan@gmail.com" target="_blank">ncoghlan@gmail.com</a>>
wrote:<br>
</div>
<div>
<blockquote type="cite">
<div>
<div><span style="color: rgb(0, 0, 0);
font-family: Helvetica,Arial,sans-serif;"><br>
</span>
For *nix, I think there is a simple way forward
that is an improvement<br>
over where things stand now. For Windows, I
don't think we can do much<br>
better than the status quo and for Mac OS X... I
think Apple will do<br>
whatever Apple feel like doing :)</div>
</div>
</blockquote>
<span> </span></div>
</div>
<div>Apple will generally follow what we decide to do for
the base install. </div>
<div><br>
</div>
<div>Anyway, I'd say that OSX should do the same as Unix
platforms here and support '#!/usr/bin/env python2'.
Adding another symlink is fairly trivial.</div>
<div><br>
</div>
<font color="#888888">
<div>Ronald</div>
</font>
<div><br>
</div>
<div>P.S. I'm a bit confused about this discussion though,
wouldn't adding python2 to the installation be a feature
change and as such not something that can be done in a
maintenance branch?</div>
</div>
<br>
_______________________________________________<br>
Python-Dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:Python-Dev@python.org" target="_blank">Python-Dev@python.org</a><br>
<a moz-do-not-send="true"
href="http://mail.python.org/mailman/listinfo/python-dev"
target="_blank">http://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a moz-do-not-send="true"
href="http://mail.python.org/mailman/options/python-dev/mail%40kerrickstaley.com"
target="_blank">http://mail.python.org/mailman/options/python-dev/mail%40kerrickstaley.com</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Python-Dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Python-Dev@python.org">Python-Dev@python.org</a>
<a class="moz-txt-link-freetext" href="http://mail.python.org/mailman/listinfo/python-dev">http://mail.python.org/mailman/listinfo/python-dev</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk">http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.voidspace.org.uk/">http://www.voidspace.org.uk/</a>
May you do good and not evil
May you find forgiveness for yourself and forgive others
May you share freely, never taking more than you give.
-- the sqlite blessing <a class="moz-txt-link-freetext" href="http://www.sqlite.org/different.html">http://www.sqlite.org/different.html</a>
</pre>
</body>
</html>