Python 3.1: Stabilization and news item
On Fri, Mar 26, 2010 at 05:27:46PM +0000, Jeremy Olexa wrote:
> On Fri, 26 Mar 2010 16:28:29 +0000, Alec Warner <email@example.com>
> > On Fri, Mar 26, 2010 at 4:08 PM, Dale <firstname.lastname@example.org> wrote:
> >> As a user, I still think this could turn into a real mess. ??I think
> >> will be quite a few that will see python being updated, run
> >> and switch it to the new python. ??At that point, it is going to hit the
> >> ??I know because this is what I always do. ??News item or not, when
> >> gets updated, I run python-updater and make sure it is selected.
If you don't bother reading news items or messages from packages, there
is nothing we can do. I don't feel that this is an excuse for holding
> * Messages for package dev-lang/python-3.1.2:
> * WARNING!
> * Many Python modules haven't been ported yet to Python 3.*.
> * Python 3 hasn't been activated and Python wrapper is still configured
> to use Python 2.
> * You can manually activate Python 3.1 using `eselect python set
> * It is recommended to currently have Python wrapper configured to use
> Python 2.
> * Having Python wrapper configured to use Python 3 is unsupported.
The message above looks pretty clear to me. It works, but don't make it
the default. Having it marked "stable" and being able to use it as the
default python are two separate things, and the maintainer is making it
very clear in this message that it can't be the default python.