Ebuilds for >=net-proxy/obfsproxy-0.2 should: 1. (R)DEPEND on dev-python/pyyaml. 2. Remove `argparse' from `install_requires' in the `setup.py' file, since argparse is already a standard library in Python 2.7+ and 3.x. Reproducible: Always Steps to Reproduce: 1. Ensure dev-python/pyyaml is uninstalled, and version of python2 is >=2.7. 2. # emerge obfsproxy 3. $ obfsproxy Actual Results: Traceback (most recent call last): File "/usr/lib/python-exec/python2.7/obfsproxy", line 5, in <module> from pkg_resources import load_entry_point File "/usr/lib64/python2.7/site-packages/pkg_resources.py", line 2716, in <module> working_set.require(__requires__) File "/usr/lib64/python2.7/site-packages/pkg_resources.py", line 685, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib64/python2.7/site-packages/pkg_resources.py", line 588, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: argparse (The same also goes for argparse.) Expected Results: obfsproxy(1) should run without the above-mentioned exceptions.
My fault, but >=net-proxy/obfsproxy-0.2 should also (R)DEPEND on virtual/python-argparse, for obvious reasons.
Thanks for the report and fix. I just added 0.2.8 to the tree. Can you please test and see that this is working now. Reopen the bug if its still broken. Note: I added virtual/python-argparse and dev-python/pyyaml to RDEPENDS only. I don't think it DEPENDS on them.