Steve Holden wrote: > Look in the build instructions for "alt-install", and make sure that you > *know* when you install the new Python that it isn't touching the system > Python at all. Always run make -n install and check what the script will > do before running it until you know what you are doing. Then run 3.x > from (somewhere like) /usr/local/bin.
We anticipated the issue during the development cycle of py3k. The 3.x series doesn't install a "python" command when it's installed with "make install". $ make install [...] * Note: not installed as 'python'. * Use 'make fullinstall' to install as 'python'. * However, 'make fullinstall' is discouraged, * as it will clobber your Python 2.x installation. Christian _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
