1 |
On Sun, Oct 19, 2014 at 1:36 PM, W. Trevor King <wking@×××××××.us> wrote: |
2 |
> On Sat, Oct 18, 2014 at 08:57:58PM -0400, Mike Gilbert wrote: |
3 |
>> This resolves a testing failure in dev-python/cryptography-1.6.1. |
4 |
>> |
5 |
>> cryptography.hazmat.backends._available_backends() scans the |
6 |
>> available setuptools entry_points, and so depends on having a valid |
7 |
>> egg-info/entry_points.txt file available. |
8 |
> |
9 |
> This sounds like the issue fixed by my Setuptools patch [1,2]. If I |
10 |
> can reproduce the test failure and confirm that my Setuptools patch |
11 |
> fixes it, can we use my patch when building Setuptools until it lands |
12 |
> upstream? |
13 |
> |
14 |
|
15 |
That looks related, but I'm not sure it would resolve the problem with |
16 |
dev-python/cryptography. |
17 |
|
18 |
Would you mind testing that to confirm? You would want to install a |
19 |
copy of setuptools with your patch applied, remove RESTRICT=test in |
20 |
cryptography-1.6.1, and then run the tests via the ebuild. |