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