The current stable version (1.9.1-r1) still installs distribute instead of setuptools when creating a Python 3 virtualenv. distribute has been merged back into setuptools [1] and is now deprecated. Meanwhile, setuptools is now compatible with both Python 2 & 3, so there's no legitimate reason for distribute to be propagated any further. In case anyone is concerned that setuptools itself is not ready since the merge, don't be: post-merge version (=dev-python/setuptools-0.8-r1) is actually already stable in the Portage tree (I realize virtualenv uses its own bundled copy - I'm just providing this as a data point). As far as bug reports go, there was only one (bug #482360), but that was back on 2013-08-24 and it was a problem with a misnamed DOCS file in the ebuild itself. [1] http://pythonhosted.org/setuptools/merge.html
Sounds good to me!
requires: =dev-python/setuptools-1.1.6 =dev-python/pypy-2.0.2 =virtual/pypy-2.0.2
(In reply to Elijah "Armageddon" El Lazkani (amd64 AT) from comment #2) > requires: > =dev-python/pypy-2.0.2 > =virtual/pypy-2.0.2 Err, no. The PyPy flags are stable-masked.
I also don't see where =dev-python/setuptools-1.1.6 is required. I've had =dev-python/virtualenv-1.10.1 keyworded and installed for over a week. Portage has never asked me to keyword setuptools as a result, and my installed version has been and continues to be the stable =dev-python/setuptools-0.8-r1.
I'm sorry for the confusion happening with python, TARGETS are throwing off the tests. amd64: pass
+ 19 Nov 2013; Tony Vroon <chainsaw@gentoo.org> virtualenv-1.10.1.ebuild: + Marked stable on AMD64 based on arch testing by Elijah "Armageddon" El + Lazkani in bug #490816.
arm stable
ppc stable
ppc64 stable
x86 stable. Closing.
