From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#46610: Interactive mode tagging for python.el navigation functions Date: Thu, 18 Feb 2021 19:25:43 +0200 Message-ID: <834ki95luw.fsf@gnu.org> References: <878s7ly57x.fsf@gnus.org> <83czwx5tfu.fsf@gnu.org> <835z2p5s9e.fsf@gnu.org> <4419101f-a65a-6906-2cdd-d550f5f40f0a@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36682"; mail-complaints-to="usenet@ciao.gmane.io" Cc: ddavis@ddavis.io, larsi@gnus.org, 46610@debbugs.gnu.org, monnier@iro.umontreal.ca To: Dmitry Gutov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Feb 18 18:42:10 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lCnJa-0009QW-4W for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 18 Feb 2021 18:42:10 +0100 Original-Received: from localhost ([::1]:42624 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCnJZ-0000Rd-1r for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 18 Feb 2021 12:42:09 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58848) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lCn3y-0002Ol-Oh for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2021 12:26:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36337) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lCn3y-0000QY-HJ for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2021 12:26:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lCn3y-0004HM-Db for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2021 12:26:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 18 Feb 2021 17:26:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46610 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: fixed Original-Received: via spool by 46610-submit@debbugs.gnu.org id=B46610.161366915716438 (code B ref 46610); Thu, 18 Feb 2021 17:26:02 +0000 Original-Received: (at 46610) by debbugs.gnu.org; 18 Feb 2021 17:25:57 +0000 Original-Received: from localhost ([127.0.0.1]:47883 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lCn3p-0004Gw-HE for submit@debbugs.gnu.org; Thu, 18 Feb 2021 12:25:57 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:40906) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lCn3n-0004GZ-UX for 46610@debbugs.gnu.org; Thu, 18 Feb 2021 12:25:52 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46818) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCn3h-0000JY-Rj; Thu, 18 Feb 2021 12:25:45 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3479 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lCn3T-0003iI-BI; Thu, 18 Feb 2021 12:25:39 -0500 In-Reply-To: <4419101f-a65a-6906-2cdd-d550f5f40f0a@yandex.ru> (message from Dmitry Gutov on Thu, 18 Feb 2021 17:37:37 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:200275 Archived-At: > Cc: ddavis@ddavis.io, larsi@gnus.org, 46610@debbugs.gnu.org, > monnier@iro.umontreal.ca > From: Dmitry Gutov > Date: Thu, 18 Feb 2021 17:37:37 +0200 > > > Not necessarily "newer", but one that relies on features that exist in > > the Emacs version with which it is bundled. > > This can be done with either maintaining a separate version of python.el > somewhere in a different repo, or with version checks inside the main > file, compatibility aliases, etc. > > Neither seems warranted for the feature in question, since we have a > backward-compatible syntax as well. My question is more of the conceptual kind, not necessarily about this specific change. Your original response was also about the principle, AFAIU. > >> 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. > > Emacs 27 users can install the most recent version of python.el from GNU > ELPA. This is generally a good thing. Sure, but if the ELPA version doesn't have these changes, there's no problem, right? > >> 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? > > I meant the "new features" of python.el (not of Emacs 28 core) and of > other "ELPA core" packages. Those new features are not merged to python.el in master branch of the Emacs repository? If they are, then users of older Emacsen can have them from ELPA, while those who use the development version will have them from master. Right?