| 1 |
Le lundi 25 octobre 2010 à 19:44 +0530, Nirbheek Chauhan a écrit : |
| 2 |
> On Mon, Oct 25, 2010 at 7:07 PM, Arfrever Frehtes Taifersar Arahesis |
| 3 |
> <Arfrever@g.o> wrote: |
| 4 |
> > I would like to suggest that setting Python 3.1 as main active version of Python be officially |
| 5 |
> > supported and recommended for Gentoo developers since 2010-12-01. Majority of packages supporting |
| 6 |
> > only Python 2.* have been prepared to work correctly in situation when Python 3.* is set as main |
| 7 |
> > active version of Python. I would like to encourage other developers to work on fixing remaining |
| 8 |
> > packages. |
| 9 |
> > |
| 10 |
> |
| 11 |
> I do not think this is a useful expenditure of developer time. There's |
| 12 |
> absolutely no hurry to start using Python 3 since 99.9% of upstreams |
| 13 |
> do not have officially supported ports yet. We can revisit this when |
| 14 |
> the upstreams of half the packages in-tree start using Python 3 by |
| 15 |
> default (this will probably take more than a year). |
| 16 |
> |
| 17 |
|
| 18 |
to reply to you and Fabio, note that Arfrever is not suggesting you |
| 19 |
start using python3. |
| 20 |
|
| 21 |
He suggests you have it as your default python interpreter which does |
| 22 |
not mean applications will magically start using it. |
| 23 |
|
| 24 |
It will however allow easier spotting of application that have not been |
| 25 |
prepared by ebuilds to run correctly with /usr/bin/python |
| 26 |
or /usr/bin/env python being python3 by default. |
| 27 |
|
| 28 |
The fix is generally easy, lots of gnome ebuilds have been fixed for |
| 29 |
gnome 2.32 and we expect the situation to be fully handled when it will |
| 30 |
be unmasked. |
| 31 |
|
| 32 |
-- |
| 33 |
Gilles Dartiguelongue <eva@g.o> |
| 34 |
Gentoo |
Archives