Re: [gentoo-dev] [News item review] Python preference to follow PYTHON_TARGETS

2021-01-24 Thread Rich Freeman
On Sun, Jan 24, 2021 at 2:09 PM Michał Górny  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  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



Re: [gentoo-dev] [News item review] Python preference to follow PYTHON_TARGETS

2021-01-24 Thread Michał Górny
On Sun, 2021-01-24 at 13:53 -0500, Rich Freeman wrote:
> On Sun, Jan 24, 2021 at 7:21 AM Michał Górny  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?

-- 
Best regards,
Michał Górny





Re: [gentoo-dev] [News item review] Python preference to follow PYTHON_TARGETS

2021-01-24 Thread Rich Freeman
On Sun, Jan 24, 2021 at 7:21 AM Michał Górny  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.

-- 
Rich



Re: [gentoo-dev] [News item review] Python preference to follow PYTHON_TARGETS

2021-01-24 Thread Michał Górny
On Sun, 2021-01-24 at 13:25 +0100, Toralf Förster wrote:
> On 1/24/21 1:21 PM, Michał Górny wrote:
> > Please review the news item inlined below.
> 
> What about a tl;dr line explaining whether dev-lang/python-exec is 
> optionally or mandatory -or better said - if/which user action is expected?
> 

Sent v2.

-- 
Best regards,
Michał Górny





Re: [gentoo-dev] [News item review] Python preference to follow PYTHON_TARGETS

2021-01-24 Thread Ionen Wolkens
On Sun, Jan 24, 2021 at 01:25:13PM +0100, Toralf Förster wrote:
> What about a tl;dr line explaining whether dev-lang/python-exec is 
> optionally or mandatory -or better said - if/which user action is expected?
As I understand it user doesn't have anything to do other than either
accept or refuse the CONFIG_PROTECT changes.

Exception could be if they were heavily relying on eselect python to
change on-the-fly using scripts or whatnot.

I originally felt this could go without a news item myself but I did see
a lot of confused users believe eselect python is essential, so an
explanation makes sense.
-- 
ionen


signature.asc
Description: PGP signature


Re: [gentoo-dev] [News item review] Python preference to follow PYTHON_TARGETS

2021-01-24 Thread Toralf Förster

On 1/24/21 1:21 PM, Michał Górny wrote:

Please review the news item inlined below.


What about a tl;dr line explaining whether dev-lang/python-exec is 
optionally or mandatory -or better said - if/which user action is expected?


--
Toralf
PGP 23217DA7 9B888F45



OpenPGP_signature
Description: OpenPGP digital signature