Dnia 2015-02-07, o godz. 16:54:54 Mike Gilbert <[email protected]> napisał(a):
> On Sat, Feb 7, 2015 at 3:38 PM, Michał Górny <[email protected]> wrote: > > Hi, > > > > Just a quick idea: > > > > 1. we set default PYTHON_SINGLE_TARGET to 3.* matching PYTHON_TARGETS, > > > > 2. python2.7-only ebuilds get implicit 2.7 via axs' patch, > > > > 3. py2.7+pypy ebuilds -- we enable 2.7 via package.use. > > Does #3 actually work if PYTHON_SINGLE_TARGET=python3_3 is in > make.conf? I forget what our findings were on this. I forgot as well. Though I think we were trying IUSE defaults then. > > Goals: > > > > a. have as high coverage as possible of ebuilds that can be installed > > with default USE set. > > > > b. Make it cleaner to install py3-only ebuilds. Right now, user gets to > > enable 3.* manually, and then maintain the entry whenever 3.* is > > upgraded to newer version. > > > > c. Improve 2.7+3.* ebuilds by replacing 2.7 with the faster & better > > 3.* :). > > > > d. Make it easier to switch 3.* version. When user wants to change it > > from 3.3 to 3.4 or the other way around, he just needs to adjust PST > > and 2.7+pypy ebuilds still work fine. > > > > Your thoughts? > > I like the idea of moving to python3 for packages that support it. > > Maybe we should try to do this in conjunction with the python3.4 > switch (again)? I haven't reviewed the stablereq tracker, but I've > seen plenty of bugmail flying by on that. Sounds about right :D. -- Best regards, Michał Górny
pgpea7T3SgQ8x.pgp
Description: OpenPGP digital signature
