| 1 |
*On Sat, Sep 19, 2009 at 23:21, Robert Bridge <robert@××××××××.com> wrote: |
| 2 |
> So the question isn't SHOULD python-3 be stabilised, it's what will break if |
| 3 |
> it is surely? |
| 4 |
|
| 5 |
There seems to be a misunderstanding on what will happen if/when |
| 6 |
python 3 gets stabilized. |
| 7 |
|
| 8 |
The short answer is... *drum roll*... nothing :) |
| 9 |
|
| 10 |
I'm guessing that the idea of getting python 3 stable is to allow |
| 11 |
people interested in using it to do so easily. We're talking about the |
| 12 |
stabilization of python 3, NOT switching portage or your system to it. |
| 13 |
|
| 14 |
Python 2.6 will continue to be the user's default python even after he |
| 15 |
installs version 3. In fact, if you're using ~testing you should have |
| 16 |
it already and your system is probably still working OK :) |
| 17 |
|
| 18 |
Now.. if a user decides to switch his system *manually* to python 3 |
| 19 |
without thinking... he's asking for it :) |
| 20 |
|
| 21 |
-- |
| 22 |
Alex || wired |
| 23 |
Gentoo Dev |
| 24 |
www.linuxized.com |
Archives