| 1 |
On Sat, Feb 7, 2015 at 3:38 PM, Michał Górny <mgorny@g.o> wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> Just a quick idea: |
| 5 |
> |
| 6 |
> 1. we set default PYTHON_SINGLE_TARGET to 3.* matching PYTHON_TARGETS, |
| 7 |
> |
| 8 |
> 2. python2.7-only ebuilds get implicit 2.7 via axs' patch, |
| 9 |
> |
| 10 |
> 3. py2.7+pypy ebuilds -- we enable 2.7 via package.use. |
| 11 |
|
| 12 |
Does #3 actually work if PYTHON_SINGLE_TARGET=python3_3 is in |
| 13 |
make.conf? I forget what our findings were on this. |
| 14 |
> |
| 15 |
> |
| 16 |
> Goals: |
| 17 |
> |
| 18 |
> a. have as high coverage as possible of ebuilds that can be installed |
| 19 |
> with default USE set. |
| 20 |
> |
| 21 |
> b. Make it cleaner to install py3-only ebuilds. Right now, user gets to |
| 22 |
> enable 3.* manually, and then maintain the entry whenever 3.* is |
| 23 |
> upgraded to newer version. |
| 24 |
> |
| 25 |
> c. Improve 2.7+3.* ebuilds by replacing 2.7 with the faster & better |
| 26 |
> 3.* :). |
| 27 |
> |
| 28 |
> d. Make it easier to switch 3.* version. When user wants to change it |
| 29 |
> from 3.3 to 3.4 or the other way around, he just needs to adjust PST |
| 30 |
> and 2.7+pypy ebuilds still work fine. |
| 31 |
> |
| 32 |
> Your thoughts? |
| 33 |
|
| 34 |
I like the idea of moving to python3 for packages that support it. |
| 35 |
|
| 36 |
Maybe we should try to do this in conjunction with the python3.4 |
| 37 |
switch (again)? I haven't reviewed the stablereq tracker, but I've |
| 38 |
seen plenty of bugmail flying by on that. |
Archives