| 1 |
On Mon, 29 Apr 2013 21:27:58 -0400 |
| 2 |
Mike Gilbert <floppym@g.o> wrote: |
| 3 |
|
| 4 |
> On Mon, Apr 29, 2013 at 4:47 PM, Dirkjan Ochtman <djc@g.o> wrote: |
| 5 |
> > On Mon, Apr 29, 2013 at 8:53 PM, Patrick McLean <chutzpah@g.o> wrote: |
| 6 |
> >> Python-3.3.1 is now in the tree and passes all tests and none of the bugs in |
| 7 |
> >> the Python 3.3 tracker (437322) appear to be blockers. I want add Python 3.3 |
| 8 |
> >> to ~arch in 7 days (on May 6th). |
| 9 |
> >> |
| 10 |
> >> Does anyone have any objections to this? |
| 11 |
> > |
| 12 |
> > I have none, but Mike G. should sign off on it before you go ahead, IMO. |
| 13 |
> > |
| 14 |
> |
| 15 |
> As I indicated in IRC, it's ok by me. |
| 16 |
> |
| 17 |
> Arfrever brought up a good point: we should adjust the default value |
| 18 |
> of PYTHON_TARGETS as specified in the base profile. I think we will |
| 19 |
> need to include both python3_2 and python3_3 until dev-lang/python-3.3 |
| 20 |
> has been stabilized on relevant archs. |
| 21 |
|
| 22 |
We shouldn't have two versions of Python 3 enabled by default. This |
| 23 |
will result in packages supporting only one of them to push |
| 24 |
REQUIRED_USE on users. |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Best regards, |
| 29 |
Michał Górny |
Archives