1 |
On Mon, 29 Aug 2022 12:14:59 +0300 |
2 |
Alexander Kurakin <kuraga333@××××.ru> wrote: |
3 |
|
4 |
> As known, `python_gen_cond_dep` is for single implementation |
5 |
> packages (either `python-single-r1` or `distutils-r1` with |
6 |
> `DISTUTILS_SINGLE_IMPL=1`) where we're depending on Python packages |
7 |
> which support multiple dependencies. (Thanks Sam James.) |
8 |
> |
9 |
> But in dev-python/twisted [1] we have both: without |
10 |
> `python_gen_cond_dep` (line 27) and with `python_gen_cond_dep` (line |
11 |
> 58). Both of these dependencies are `PYTHON_COMPAT=( python3_{8..11} |
12 |
> pypy3 )` + `inherit distutils-r1` + no set for |
13 |
> `DISTUTILS_SINGLE_IMPL`: [2], [3]. |
14 |
> |
15 |
> What's the difference? Thanks! |
16 |
|
17 |
In twisted's BDEPEND calls to python_gen_cond_dep, Python impl names |
18 |
are passed after the depstring, and this looks like a way to limit |
19 |
those dependencies to certain impls. python3_11 is omitted compared |
20 |
to PYTHON_COMPAT so maybe the tests don't support that yet. |
21 |
|
22 |
Note that python_gen_cond_dep from python-r1.eclass is different from |
23 |
python-single-r1.eclass, it generates dependencies using |
24 |
PYTHON_TARGETS instead of PYTHON_SINGLE_TARGETS. |
25 |
|
26 |
Cheers, |
27 |
Bryan |
28 |
|
29 |
> Sincerely, |
30 |
> Alexander Kurakin. |