With the decision to have references to py3k scripts always contain a
"3", I agree that "make fullinstall" is no longer appropriate.
With r72723 and current py3k, however, there are still some issues.
Compare ls -l bin from 2.6.2, 3.0.1, and current py3k:
$ cd /Library/Frameworks/Python.framework/Versions
$ ls -l 2.6/bin
total 264
-rwxrwxr-x 1 root admin 150 Apr 16 00:28 2to3*
lrwxr-xr-x 1 root admin 7 May 21 23:57 idle@ -> idle2.6
-rwxrwxr-x 1 root admin 138 Apr 16 00:28 idle2.6*
lrwxr-xr-x 1 root admin 8 May 21 23:57 pydoc@ -> pydoc2.6
-rwxrwxr-x 1 root admin 123 Apr 16 00:28 pydoc2.6*
lrwxr-xr-x 1 root admin 9 May 21 23:57 python@ -> python2.6
lrwxr-xr-x 1 root admin 16 May 21 23:57 python-config@ ->
python2.6-config
-rwxrwxr-x 1 root admin 33688 Apr 16 00:30 python2.6*
-rwxrwxr-x 1 root admin 1463 Apr 16 00:29 python2.6-config*
lrwxr-xr-x 1 root admin 10 May 21 23:57 pythonw@ -> pythonw2.6
-rwxrwxr-x 1 root admin 33688 Apr 16 00:30 pythonw2.6*
lrwxr-xr-x 1 root admin 11 May 21 23:57 smtpd.py@ -> smtpd2.6.py
-rwxrwxr-x 1 root admin 18093 Apr 16 00:28 smtpd2.6.py*
$ ls -l 3.0/bin
total 248
-rwxrwxr-x 1 root admin 150 Feb 14 10:04 2to3*
lrwxr-xr-x 1 root admin 7 May 21 23:58 idle@ -> idle3.0
-rwxrwxr-x 1 root admin 138 Feb 14 10:04 idle3.0*
lrwxr-xr-x 1 root admin 8 May 21 23:58 pydoc@ -> pydoc3.0
-rwxrwxr-x 1 root admin 123 Feb 14 10:04 pydoc3.0*
lrwxr-xr-x 1 root admin 9 May 21 23:58 python@ -> python3.0
lrwxr-xr-x 1 root admin 16 May 21 23:58 python-config@ ->
python3.0-config
-rwxrwxr-x 1 root admin 29560 Feb 14 10:05 python3.0*
-rwxrwxr-x 1 root admin 1440 Feb 14 10:05 python3.0-config*
lrwxr-xr-x 1 root admin 10 May 21 23:58 pythonw@ -> pythonw3.0
-rwxrwxr-x 1 root admin 29560 Feb 14 10:05 pythonw3.0*
lrwxr-xr-x 1 root admin 11 May 21 23:58 smtpd.py@ -> smtpd3.0.py
-rwxrwxr-x 1 root admin 18119 Feb 14 10:04 smtpd3.0.py*
$ ls -l 3.1/bin
total 272
lrwxr-xr-x 1 root admin 7 May 21 19:10 idle3@ -> idle3.1
-rwxrwxr-x 1 root admin 138 May 21 18:51 idle3.1*
lrwxr-xr-x 1 root admin 8 May 21 19:10 pydoc3@ -> pydoc3.1
-rwxrwxr-x 1 root admin 123 May 21 18:51 pydoc3.1*
-rwxrwxr-x 1 root admin 34220 May 21 18:51 python*
lrwxr-xr-x 1 root admin 16 May 21 19:10 python-config@ ->
python3.1-config
lrwxr-xr-x 1 root admin 9 May 21 19:10 python3@ -> python3.1
lrwxr-xr-x 1 root admin 16 May 21 19:10 python3-config@ ->
python3.1-config
-rwxrwxr-x 1 root admin 29560 May 21 18:51 python3.1*
-rwxrwxr-x 1 root admin 1440 May 21 18:51 python3.1-config*
lrwxr-xr-x 1 root admin 10 May 21 19:10 pythonw3@ -> pythonw3.1
-rwxrwxr-x 1 root admin 29560 May 21 18:51 pythonw3.1*
Issues:
1. In py3k bin, there is a "python" binary rather than the symlink that
was there before. That appears to be the unstripped binary of the
interpreter (before it is stripped installed into the fw app bundle).
Presumably the symlink install used to implicitly remove the binary; now
an explicit rm is needed?
2. There is still a symlink to python-config.
3. There is no longer *any* 2to3 script, versioned or not. r71936
(setup.py) is the culprit here (Issue5756, which I'm reopening to ensure
this issue is examined for all platforms). With regard to the OSX
installer, since Tools/scripts isn't installed, there needs to be a
script of some kind in bin. As discussed in Issue5756, it should be
decided how to resolve conflicts between a py2 2to3 and a py3 one.
4. There is no longer any smtpd.py or smtpd3.x.py script/link installed,
also due to r71936 (setup.py) and to r72723 (Mac/Makefile.in). I don't
see this as a huge issue since I doubt that script is used much at all.
But, at the least, a NEWS/What's New and/or README item about its
removal in 3.1 is in order.
|