public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bryan Gardiner <bog@khumba.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] About python_ge­n_cond_dep
Date: Mon, 29 Aug 2022 20:00:32 -0700	[thread overview]
Message-ID: <20220829200032.1688fd0b@khumba.net> (raw)
In-Reply-To: <1661764499.757596916@f553.i.mail.ru>

On Mon, 29 Aug 2022 12:14:59 +0300
Alexander Kurakin <kuraga333@mail.ru> wrote:

> As known, `python_gen_cond_dep` is for single implementation
> packages (either `python-single-r1` or `distutils-r1` with
> `DISTUTILS_SINGLE_IMPL=1`) where we're depending on Python packages
> which support multiple dependencies. (Thanks Sam James.)
> 
> But in dev-python/twisted [1] we have both: without
> `python_gen_cond_dep` (line 27) and with `python_gen_cond_dep` (line
> 58). Both of these dependencies are `PYTHON_COMPAT=( python3_{8..11}
> pypy3 )` + `inherit distutils-r1` + no set for
> `DISTUTILS_SINGLE_IMPL`: [2], [3].
> 
> What's the difference? Thanks!

In twisted's BDEPEND calls to python_gen_cond_dep, Python impl names
are passed after the depstring, and this looks like a way to limit
those dependencies to certain impls.  python3_11 is omitted compared
to PYTHON_COMPAT so maybe the tests don't support that yet.

Note that python_gen_cond_dep from python-r1.eclass is different from
python-single-r1.eclass, it generates dependencies using
PYTHON_TARGETS instead of PYTHON_SINGLE_TARGETS.

Cheers,
Bryan

> Sincerely,
> Alexander Kurakin.


  reply	other threads:[~2022-08-30  3:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29  9:14 [gentoo-user] About python_ge­n_cond_dep Alexander Kurakin
2022-08-30  3:00 ` Bryan Gardiner [this message]
2022-08-30 15:53   ` [gentoo-user] Re: [gentoo-user] About python_gen_cond_dep Alexander Kurakin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220829200032.1688fd0b@khumba.net \
    --to=bog@khumba.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox