bug#55027: 28.1; User option python-forward-sexp-function in wrong group

[Howard Melman <hmelman@gmail.com>]

On Apr 21, 2022, at 8:44 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Howard Melman <hmelman@gmail.com>
>> Date: Thu, 21 Apr 2022 08:06:14 -0400
>> Cc: Kévin Le Gouguec <kevin.legouguec@gmail.com>,
>> 55027@debbugs.gnu.org
>> 
>> On Apr 21, 2022, at 2:07 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>>> 
>>> I fixed it in a safer way on the release branch, thanks.
>> 
>> Why did you keep it in the python-flymake group in addition to the
>> python group?
> 
> Because it was there in Emacs 28.1.  I didn't want to make
> incompatible changes on the release branch.

I wouldn't call a change in what group an option appears in
in an interactive customize session an incompatibility.  The change
in group has nothing to do with how it's set or used.

>> It has nothing to do with flymake.  
>> 
>> Since it's a new option, you're just extending the amount of time
>> for people to get confused by it.
> 
> Confused in what way?  How can the fact that an option appears in an
> additional customization group confuse someone?

Because it will still appear in the python-flymake group and it has
nothing to do with flymake.  Anyone looking at the python-flymake
group will be confused as to why it's there. 

It was a mistake for it to be in that group in the first place, why prolong it?  
I don't see why a change in which group an option appears in can
only happen in a major release.  Fixing it sooner means fewer people
will be affected by any incompatibility.

Howard