From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: ddavis@ddavis.io, larsi@gnus.org, 46610@debbugs.gnu.org
Subject: bug#46610: Interactive mode tagging for python.el navigation functions
Date: Thu, 18 Feb 2021 16:54:37 +0200 [thread overview]
Message-ID: <c395ba90-d3ba-098d-d03f-5c441d2df45c@yandex.ru> (raw)
In-Reply-To: <83czwx5tfu.fsf@gnu.org>
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?
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.
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.
next prev parent reply other threads:[~2021-02-18 14:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 4:46 bug#46610: Interactive mode tagging for python.el navigation functions Doug Davis
2021-02-18 11:40 ` Lars Ingebrigtsen
2021-02-18 11:49 ` Dmitry Gutov
2021-02-18 11:52 ` Lars Ingebrigtsen
2021-02-18 14:41 ` Eli Zaretskii
2021-02-18 14:54 ` Dmitry Gutov [this message]
2021-02-18 15:07 ` Eli Zaretskii
2021-02-18 15:37 ` Dmitry Gutov
2021-02-18 17:25 ` Eli Zaretskii
2021-02-18 17:54 ` Dmitry Gutov
2021-02-18 19:47 ` Eli Zaretskii
2021-02-18 19:57 ` Dmitry Gutov
2021-02-18 20:00 ` Eli Zaretskii
2021-02-18 20:05 ` Dmitry Gutov
2021-02-18 15:50 ` Doug Davis
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=c395ba90-d3ba-098d-d03f-5c441d2df45c@yandex.ru \
--to=dgutov@yandex.ru \
--cc=46610@debbugs.gnu.org \
--cc=ddavis@ddavis.io \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.