The "threads" use flag disappeared from dev-lang/python:3.7, but many current ebuilds (notably sphinx) in the tree have PYTHON_REQ_USE="threads(+)" in them. This blocks use of python 3.7 for all but the sparest of installations. Should be tracked by python tracker, bug #695996. Reproducible: Always Steps to Reproduce: 1. add "python3_7" to PYTHON_TARGETS in make.conf on an up-to-date system with dev-python/sphinx installed. 2. emerge --newuse -uD world 3. emerge fails because of conflicts. Adding +threads to IUSE for python 3.7 ebuilds seems harmless enough.
(In reply to Joel Berendzen from comment #0) > The "threads" use flag disappeared from dev-lang/python:3.7, but many > current ebuilds (notably sphinx) in the tree have > PYTHON_REQ_USE="threads(+)" in them. > > This blocks use of python 3.7 for all but the sparest of installations. > > Should be tracked by python tracker, bug #695996. > > > Reproducible: Always > > Steps to Reproduce: > 1. add "python3_7" to PYTHON_TARGETS in make.conf on an up-to-date system > with dev-python/sphinx installed. > 2. emerge --newuse -uD world > 3. emerge fails because of conflicts. > > > > > Adding +threads to IUSE for python 3.7 ebuilds seems harmless enough. You do understand that PYTHON_REQ_USE="threads(+)" means "require threads, but if the flag is missing assume it is enabled". With that in mind, does this really break anything?
Per Brian's comment, please elaborate on what exactly is broken here. Raw emerge output is preferable.
