bug#46610: Interactive mode tagging for python.el navigation functions

[Eli Zaretskii]

> Cc: ddavis@ddavis.io, larsi@gnus.org, 46610@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Thu, 18 Feb 2021 16:54:37 +0200
> 
> On 18.02.2021 16:41, Eli Zaretskii wrote:
> >> python.el is distributed as "core" package through GNU ELPA and declared
> >> compatibility up to Emacs 24.1.
> >>
> >> So I don't think you can use the new 'interactive' syntax there.
> > So packages on ELPA are allowed to be ahead of those in core, but not
> > vice versa?  Is that really the intent that we allow them to diverge,
> > but only in one direction?
> 
> What do you mean by "ahead"? Have a newer version of the package in 
> 'master' and some other in ELPA?

Not necessarily "newer", but one that relies on features that exist in
the Emacs version with which it is bundled.

> Then we (someone? who?) either have to maintain both version, or accept 
> that ELPA and all users of Emacs 24-27 won't get any subsequent updates 
> to python.el, including support for newer Python syntax, etc.

I don't think I understand why.  We are talking about changing
python.el on master, which will be released with Emacs 28, in some
not-too-close future.  What does that have to do with users of older
Emacsen receiving updates to python.el?  I guess I'm confused here.

> Either approach can work in ELPA, but our "ELPA core" scheme aims to 
> make new features available to as many users as feasible, while limiting 
> the extra support effort required.

The new features on master will be available only when Emacs 28 is
released, until then they cannot possibly do any harm to anyone.
Right?