> Please rebuild dev-python/pypy:1.7 with the following USE flags enabled: threads Problems with this: - pypy doesn't have a threads USE flag; should it grow one? - the error seems to be thrown even when the mercurial ebuild restricts pypy ABI
Does build system of PyPy allow to disable support for threads? (CPython has --without-threads option.) (Actually python_pkg_setup() doesn't check USE flags for Python versions for restricted Python ABIs.)
If you temporarily remove PYTHON_USE_WITH="threads", then does installation of Mercurial for PyPy work? Does Mercurial work at run time with PyPy?
Mercurial's test suite doesn't pass on pypy, although some things work.
I have fixed this bug in Progress Overlay in r863.
*** Bug 403807 has been marked as a duplicate of this bug. ***
Is this still relevant? With new eclass etc?
I don't know. Does someone who has pypy installed want to test and report back?
PyPy has threads unconditionally on. So REQ_USE shall be 'threads(+)' for PyPy compat.
Mercurial doesn't support PyPy, PyPy doesn't claim that Mercurial works with it. After migration to new eclass mercurial won't be built for PyPy, so I suggest closing as INVALID. REQ_USE='threads(+)' would be a nice optional bonus.
Good call. Please file a separate bug about the REQ_USE thing (with patch?) with a little more elaborate justification?
(In reply to Dirkjan Ochtman from comment #10) > Good call. Please file a separate bug about the REQ_USE thing (with patch?) > with a little more elaborate justification? Well, if pypy is disabled, there's no point for (+) in REQ_USE.
