On Sun, Oct 19, 2014 at 2:04 PM, Mike Gilbert <[email protected]> wrote: > On Sun, Oct 19, 2014 at 1:36 PM, W. Trevor King <[email protected]> wrote: >> On Sat, Oct 18, 2014 at 08:57:58PM -0400, Mike Gilbert wrote: >>> This resolves a testing failure in dev-python/cryptography-1.6.1. >>> >>> cryptography.hazmat.backends._available_backends() scans the >>> available setuptools entry_points, and so depends on having a valid >>> egg-info/entry_points.txt file available. >> >> This sounds like the issue fixed by my Setuptools patch [1,2]. If I >> can reproduce the test failure and confirm that my Setuptools patch >> fixes it, can we use my patch when building Setuptools until it lands >> upstream? >> > > That looks related, but I'm not sure it would resolve the problem with > dev-python/cryptography. > > Would you mind testing that to confirm? You would want to install a > copy of setuptools with your patch applied, remove RESTRICT=test in > cryptography-1.6.1, and then run the tests via the ebuild.
Oh, my reading comprehension is not so good at the moment; I realized you just offered to do exactly that. I would certainly consider applying a patch to setuptools to resolve it, though I would prefer upstream to accept it first. I don't want to end up carrying it forever.
