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 17:37:37 +0200 Message-ID: <4419101f-a65a-6906-2cdd-d550f5f40f0a@yandex.ru> References: <878s7ly57x.fsf@gnus.org> <83czwx5tfu.fsf@gnu.org> <835z2p5s9e.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="20815"; 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 16:38:20 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 1lClNi-0005Ik-MW for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 18 Feb 2021 16:38:18 +0100 Original-Received: from localhost ([::1]:35252 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lClNg-0006z2-AH for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 18 Feb 2021 10:38:17 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44152) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lClNR-0006yr-TI for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2021 10:38:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36218) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lClNR-0000ou-LM for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2021 10:38:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lClNR-0001ZF-Hn for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2021 10:38:01 -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 15:38:01 +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.16136626696007 (code B ref 46610); Thu, 18 Feb 2021 15:38:01 +0000 Original-Received: (at 46610) by debbugs.gnu.org; 18 Feb 2021 15:37:49 +0000 Original-Received: from localhost ([127.0.0.1]:47764 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lClNF-0001Yp-Ay for submit@debbugs.gnu.org; Thu, 18 Feb 2021 10:37:49 -0500 Original-Received: from mail-ej1-f52.google.com ([209.85.218.52]:34736) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lClND-0001Yd-QA for 46610@debbugs.gnu.org; Thu, 18 Feb 2021 10:37:48 -0500 Original-Received: by mail-ej1-f52.google.com with SMTP id hs11so6406744ejc.1 for <46610@debbugs.gnu.org>; Thu, 18 Feb 2021 07:37:47 -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=ll7sirCJ5Y+TQIxQA/4lWeoF5/W0H1QqxAQtDD3GBDk=; b=GAavh7qWshnO/qkOPKfwbrYKUBnBvPKshd0w/2lPbN75TAKQPq+wnVgQganeLPyiO2 JylCOSQWJ/ULZE09C8TBlcd26nh1u4p3nuESo6ItNwVUjVJpt7ZivsQ/B4OwxvFzRnw8 MVU6uyPalZyVEZBNm7ET8p4P5pgrLkktWfkLHFQ1ibZYe6Sp5qU9oBbvpD2ejnWjviqT b55VUALc1+h4mPtH9VGaaNO2+3ISd0K/yeAzAVR/NTZNV3efXK+1o3wcPmRrcUxZFWAW 1gvQb75j9zcLbxhMCftEB7KaRt6CIxf03gfmoI5EYuqLSpNP2xQVJeWnfs9pV0nN8Rvd HtHw== 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=ll7sirCJ5Y+TQIxQA/4lWeoF5/W0H1QqxAQtDD3GBDk=; b=k2BJVjBIK8exP8uQfeRWRr9EhtUT5PEIxlTokySDlQnUb2la6lRzZnA0v8qMz2DX2h 6IUhN1TDjemAPC7aCiCjOoLgbRNOGqnK1pHS+aCrSzGg7AtEvqW3lr+JFSnBcN025r7h mndGabvkcaPEUNebYVBBbXf/N56vnMFK+bQ6oQENRr4QRF7sDhSWeLk15Td8rIgFGtzA p7IRpV5ZzIt4Pap8UJuzkLZPFgpXcYpbMfIJ6Ui4PhAQ3RnkaPqo2JetKIgIv/d5ExvZ 0JYweDZKWa/x8xQbAH+glWvqoAvJMKHW4QTRJDAMeqjhW7UEppnzzHp/v4enBGD5I5rK 4PUQ== X-Gm-Message-State: AOAM530Dn0Eyp3TDz0P1dbkFe41nwqb3bsyFc03If/+75G55VSXf0HOk lDdsD4jO7n/BKdYv0+BIEWE= X-Google-Smtp-Source: ABdhPJyGHE+CPfZ1XQtCNVlUyBR4fNsZ0pNFF3ktq0PhsqeIZNt4BGVhL3vVHq5PcBB/B56wI7IlEA== X-Received: by 2002:a17:906:8692:: with SMTP id g18mr4644401ejx.418.1613662662028; Thu, 18 Feb 2021 07:37:42 -0800 (PST) Original-Received: from [192.168.0.6] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id o10sm2800758eju.89.2021.02.18.07.37.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 Feb 2021 07:37:41 -0800 (PST) In-Reply-To: <835z2p5s9e.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:200271 Archived-At: On 18.02.2021 17:07, Eli Zaretskii wrote: >>>> 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. 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. >> 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. >> 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.