public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [News item review] Python preference to follow PYTHON_TARGETS
Date: Sun, 24 Jan 2021 15:23:33 -0500	[thread overview]
Message-ID: <CAGfcS_kUv5xurc+rh79tTvdaUPT9uRbRnANekSD33AEqiNDMfg@mail.gmail.com> (raw)
In-Reply-To: <a46cb8e744ce82d0bc368a74e8d39369d5d467ac.camel@gentoo.org>

On Sun, Jan 24, 2021 at 2:09 PM Michał Górny <mgorny@gentoo.org> wrote:
>
> On Sun, 2021-01-24 at 13:53 -0500, Rich Freeman wrote:
> > On Sun, Jan 24, 2021 at 7:21 AM Michał Górny <mgorny@gentoo.org> wrote:
> > >
> > > For this reason, we have decided to change the default python-exec
> > > configuration to match PYTHON_TARGETS by default, in the eclass
> > > preference order, that is from the newest CPython version to oldest,
> > > with alternative Python implementations coming afterwards.  This change
> > > will be propagated via the configuration protection mechanism whenever
> > > dev-lang/python-exec-conf is installed or rebuilt due to PYTHON_TARGETS
> > > changes.  This will permit the users to interactively confirm
> > > the updates.
> > >
> > > If the new default is not correct for you, please use your preferred
> > > configuration update tool to discard or edit the new configuration file.
> >
> > Could we just spell out what the actual setting is?  That way if a
> > user accepts or rejects the change accidentally it is trivial to fix,
> > vs making them hunt through the installed files to do a diff...
> >
> > Nothing wrong with the instructions - I'd just add one line about what
> > setting controls this.
> >
>
> The exact paths are provided in the second paragraph.  Am I missing
> something?
>

No - the way this works makes sense now.  For some reason I missed it
on the first two reads, which makes me suspect others will as well.
It wasn't the location of the config file I missed, but the fact that
the eclass will just do what eselect python used to do, and thus
trigger config protection (which is at the end of paragraph 4).

For some reason when I read the section about discarding the changes I
was thinking that there was some config toggle to change this behavior
vs the old way things worked.  Instead the new behavior is
unconditional, but the updates it makes to the python-exec config can
be rejected.

-- 
Rich


  reply	other threads:[~2021-01-24 20:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-24 12:21 [gentoo-dev] [News item review] Python preference to follow PYTHON_TARGETS Michał Górny
2021-01-24 12:25 ` Toralf Förster
2021-01-24 12:43   ` Ionen Wolkens
2021-01-24 12:59   ` Michał Górny
2021-01-24 12:59 ` [gentoo-dev] [News item review v2] " Michał Górny
2021-01-24 15:11   ` Thomas Deutschmann
2021-01-24 15:23     ` Hans Fernhout
2021-01-24 19:11       ` Michał Górny
2021-01-24 19:14     ` Michał Górny
2021-01-24 15:16   ` Aisha Tammy
2021-01-24 15:28     ` Ionen Wolkens
2021-01-24 19:04     ` Michał Górny
2021-01-24 18:16   ` Alexey Sokolov
2021-01-24 19:06     ` Michał Górny
2021-01-24 18:53 ` [gentoo-dev] [News item review] " Rich Freeman
2021-01-24 19:09   ` Michał Górny
2021-01-24 20:23     ` Rich Freeman [this message]
2021-01-24 19:56 ` [gentoo-dev] [News item review v3] " Michał Górny
2021-01-25 22:12 ` [gentoo-dev] [News item review v4] " Michał Górny
2021-01-26  6:39   ` Philip Webb
2021-01-30 12:13     ` Michał Górny

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=CAGfcS_kUv5xurc+rh79tTvdaUPT9uRbRnANekSD33AEqiNDMfg@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@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