On Fri, Nov 14, 2008 at 9:48 AM, Terry Reedy <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: >> >> No, no, no! *Eventually* Python 3.0 will just be "python". Until >> then, it needs to be "python3.0". > > I think you should consider changing the installation policy to installing > each file with its own pythonx.y name and alias exactly one, the system > default, as 'python'.
Um, we already do this, unless I misunderstand your proposal. For any 2.x (and even 1.x) version, "make altinstall" installs only pythonx.y, and "make install" creates a link to it named "python". For 3.0, "install" is equal to "altinstall" because making 3.0 the default is not realistic at this time. At some point in the future we can revisit this. > Multiple installations are going to be common for > several years, I suspect. And have been forever. > Currently on Windows, python3.0 is installed as just plain 'python'. This > already causes problems when I want to choose 2.5 or 3.0. In my quick start > list, I have two entries which both say "Python (command line)" with the > *same* icon. Switching to admin, I just renamed one to Python2.5..., but > that changes it also in the Python25 start menu directory, so I do not know > if the change will survive the upgrade to 2.5.3. Duplicate names are also a > problem for the right-click-on-.py-file context menu. It would be really > helpful if there was a new icon for 3.0. Ah, Windows. Can you file a bug about this? I think only MvL can do something about this. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
