No, no, no!  *Eventually* Python 3.0 will just be "python". Until
then, it needs to be "python3.0".

Long agon, Red Hat installed Python 2 as "python2" instead of "python"
and it led to endless problems.

On Wed, Nov 12, 2008 at 12:46 PM, Smith-Rowland, Edward M
<[EMAIL PROTECTED]> wrote:
>
> When I try to install python-3.0rcN I get the following warning:
>
> running install_egg_info
> Writing /usr/local/lib/python3.0/lib-dynload/Python-3.0rc2-py3.0.egg-info
> * 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.
>
> Not clobbering my python-2.* install is all well and good.  python-3.0 is 
> installed as expected.
>
> It would be nice to have a generic way to call python-3 though.
>
> Suggestion: Use python3 as the generic install target for python-3.*
> Then all subsequent python-3.* installs would get sent there (in addition to 
> python-3.m.n)
>
> If no python2 exists you could either go ahead and use that for python3.
> Or you could leave the python just for 2.
>
> Ed
> _______________________________________________
> 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/guido%40python.org
>



-- 
--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

Reply via email to