all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ddavis@ddavis.io, larsi@gnus.org, 46610@debbugs.gnu.org,
	monnier@iro.umontreal.ca
Subject: bug#46610: Interactive mode tagging for python.el navigation functions
Date: Thu, 18 Feb 2021 21:57:56 +0200	[thread overview]
Message-ID: <a9bcbf4f-7bd0-c294-a5e8-cf4e36c18adf@yandex.ru> (raw)
In-Reply-To: <83v9ap40qf.fsf@gnu.org>

On 18.02.2021 21:47, Eli Zaretskii wrote:
>> Cc: ddavis@ddavis.io, larsi@gnus.org, 46610@debbugs.gnu.org,
>>   monnier@iro.umontreal.ca
>> From: Dmitry Gutov <dgutov@yandex.ru>
>> Date: Thu, 18 Feb 2021 19:54:06 +0200
>>
>>> My question is more of the conceptual kind, not necessarily about this
>>> specific change.  Your original response was also about the principle,
>>> AFAIU.
>>
>> I guess I'm not sure what you are asking about at this point
> 
> Let me repeat my original question:

Very good.

>> 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?
> 
>> yes, python.el is allowed to incorporate support for some new
>> features from Emacs 28, as long as they are backward-compatible, or
>> gated behind a version check.
> 
> If python.el in emacs.git is allowed to be different from that in
> elpa.git (and AFAIU we already allow that), then there should be no
> need for any compatibility shims in the version that is in emacs.git.

Then this part of my first reply should be most pertinent:

     Then we (someone? who?) either have to maintain both versions

Emphasis on "who".





  reply	other threads:[~2021-02-18 19:57 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
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 [this message]
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=a9bcbf4f-7bd0-c294-a5e8-cf4e36c18adf@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.