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.


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?

-- 
Best regards,
Michał Górny

Attachment: pgpRojCVqfkrE.pgp
Description: OpenPGP digital signature

Reply via email to