From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#46610: Interactive mode tagging for python.el navigation functions Date: Thu, 18 Feb 2021 19:54:06 +0200 Message-ID: <253198f6-9ebb-f348-7dbe-a44d3d9281a8@yandex.ru> References: <878s7ly57x.fsf@gnus.org> <83czwx5tfu.fsf@gnu.org> <835z2p5s9e.fsf@gnu.org> <4419101f-a65a-6906-2cdd-d550f5f40f0a@yandex.ru> <834ki95luw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24744"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 Cc: ddavis@ddavis.io, larsi@gnus.org, 46610@debbugs.gnu.org, monnier@iro.umontreal.ca To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Feb 18 18:56:52 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 1lCnXm-0006HL-Os for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 18 Feb 2021 18:56:50 +0100 Original-Received: from localhost ([::1]:45576 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCnXl-0005kY-OX for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 18 Feb 2021 12:56:49 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38736) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lCnW3-00048Y-2y for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2021 12:55:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36350) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lCnW2-0004OS-Q5 for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2021 12:55:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lCnW2-0004yQ-HF for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2021 12:55:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 18 Feb 2021 17:55: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.161367086119059 (code B ref 46610); Thu, 18 Feb 2021 17:55:02 +0000 Original-Received: (at 46610) by debbugs.gnu.org; 18 Feb 2021 17:54:21 +0000 Original-Received: from localhost ([127.0.0.1]:47896 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lCnVJ-0004xG-AQ for submit@debbugs.gnu.org; Thu, 18 Feb 2021 12:54:21 -0500 Original-Received: from mail-ej1-f44.google.com ([209.85.218.44]:37996) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lCnVH-0004x4-Lo for 46610@debbugs.gnu.org; Thu, 18 Feb 2021 12:54:16 -0500 Original-Received: by mail-ej1-f44.google.com with SMTP id bl23so7111075ejb.5 for <46610@debbugs.gnu.org>; Thu, 18 Feb 2021 09:54:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=J7FVV121XYhdSxlNPiyRf4NwAe+lm2Yn4EgagSQmIO8=; b=QGzXJ9b81OAWJzGi/T0rso5CCbNOQ0deflN2YE6TU5e0Bzr377LZ902d1dsNsRmnqT J17ql4lQA72/gtbtqRo2HXSVtlwULUlZ/bf5u6VspvHJuUCCkPm11XK3EjVv1UADFgWW X9eqg3GaBgGeaAnLXYOc4FFYaPBzT9eY7hYEj8a8ObK+N7+deHGJHljjV/RodIiw+1i1 PwOLijx1LMucq5OX7O+cXqJ/k2nj3d7eQfw4ap3Iak/4OIkc+r6MekZCoOv4e0LbwTUr BebXdUEkWZdD5n94SdhvydoAlr7MzeKHA+Ld85KQ4B2ovmDbBlOfTFIKj7xbF55Dg6Cm jxsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=J7FVV121XYhdSxlNPiyRf4NwAe+lm2Yn4EgagSQmIO8=; b=hAlqNFZQS1hsQav8M1mredRSxIthMTBGLAZCaWWHwN63RnPHqeJLsGtJ+9/yGiAJQF k8EbdHQ9vjHqRILMaygiYK2odPEjy9yE7Ej1DBF5Mjhe0qlYj+sGItzCGEodCQOSx/PX /RCTnXTolfj/02puWCeRS5y16Fnkf/jBEaQuaGsZqhEnCWIplw9svyJytqyNyqf+MZsy p/69JKUiqpCE/mBRLFgKBbjZVHuzrGXDH0cpcArVj7Ptp7uWxxUVEHhyKDO0mqfLleBV Diutlh7Kl+uXBQZvPklWnzZOOxKDycAOwwyIDgPT6ncn0jGlifRIZ2AUBRt2XD+mizZQ 1kmQ== X-Gm-Message-State: AOAM530FNSQG6R1fUGxsqR0AX4AzFCmQ/r8b90CSb35zS6ogEValcwOI sqq/7gQpo9K9UokVAiNk/GE= X-Google-Smtp-Source: ABdhPJyYPJX+H5F5fvODWd+mWiB+vpqiAfStn8GlSivyxJgchN+wFCM3O+WQYGzYFfOGHgxpzt3QQA== X-Received: by 2002:a17:906:3603:: with SMTP id q3mr4841045ejb.201.1613670849634; Thu, 18 Feb 2021 09:54:09 -0800 (PST) Original-Received: from [192.168.0.6] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id l61sm804324edl.37.2021.02.18.09.54.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 Feb 2021 09:54:09 -0800 (PST) In-Reply-To: <834ki95luw.fsf@gnu.org> Content-Language: en-US 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:200276 Archived-At: On 18.02.2021 19:25, Eli Zaretskii wrote: >> 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. I guess I'm not sure what you are asking about at this point, so I'm trying to cover all the bases: 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. Speaking about "conceptual" replies, I don't really care for python.el personally, but I've been thinking of making ruby-mode.el an "ELPA core" package too. >>>> 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? The problem might be users missing some features that had been added to python.el in emacs.git master in the meantime. >>>> 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? emacs.git master is the "upstream" for python.el, so "new features" and "features merged to python.el in master branch of the Emacs repository" describe the same thing. > 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? That's how it works, yes.