On Fri, May 1, 2015 at 9:12 AM, Ben Finney <ben+pyt...@benfinney.id.au> wrote: > Chris Angelico <ros...@gmail.com> writes: > >> Very easily and simply: Python 3 and Python 2 will always install >> separately, and the only possible conflicts are over the "python" >> command in PATH and which program is associated with ".py" files. > > Calling ‘python’ is now ambiguous, and with Python 2 slipping inexorably > into the past, increasingly the ‘python’ command is the wrong choice for > code that we want to survive in the future. > > I am seeing a growing call, with which I agree, to recommend explicitly > calling ‘python2’ or ‘python3’ as commands. >
Agreed. And on Windows, the "py -3" or "py -2" options are also available. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
