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 16:54:37 +0200 Message-ID: References: <878s7ly57x.fsf@gnus.org> <83czwx5tfu.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="36022"; 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 To: Eli Zaretskii , Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Feb 18 15:58:05 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 1lCkkn-0009GY-Mp for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 18 Feb 2021 15:58:05 +0100 Original-Received: from localhost ([::1]:52428 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCkkm-0004MH-N3 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 18 Feb 2021 09:58:04 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34334) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lCkhq-000269-3s for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2021 09:55:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34964) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lCkhp-0006xB-Qu for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2021 09:55:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lCkhp-0000C7-Ph for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2021 09:55: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 14:55: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.1613660087720 (code B ref 46610); Thu, 18 Feb 2021 14:55:01 +0000 Original-Received: (at 46610) by debbugs.gnu.org; 18 Feb 2021 14:54:47 +0000 Original-Received: from localhost ([127.0.0.1]:46509 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lCkhb-0000BX-GT for submit@debbugs.gnu.org; Thu, 18 Feb 2021 09:54:47 -0500 Original-Received: from mail-ed1-f45.google.com ([209.85.208.45]:37251) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lCkhZ-0000BL-Hv for 46610@debbugs.gnu.org; Thu, 18 Feb 2021 09:54:45 -0500 Original-Received: by mail-ed1-f45.google.com with SMTP id o3so4735353edv.4 for <46610@debbugs.gnu.org>; Thu, 18 Feb 2021 06:54:45 -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=qZrJYoykwf3ME+oUDv+0yLazMZ6AQoVFLJRi5UWvX1A=; b=ZVbKcwycTEhIrsa0YqOD1htvzbHQ41CywsqbavlNV9GruZFekFYuuhN/dKLiv+MQzd QKRrNgiD5TuxhWlwRvUVJ+ndy6AhDRlDC2OqWCdhCI0pxcZ1Kk6VXDh4IeWShdEVQNwn loB907Fy/8I0BGRN2yK0zRm3Pbf/Zm27i2iQ1u1TwTt2RAEvRvNxNZBUehdLRIZ+S+b8 oCEMAGmNFwUq07R/yxSzeVBu7n8sDlQT8NLGlO/z3GT+K87q5ewzFFogPTdcdcEcgh1m v4wgLLoDzTyN2Dz/n3VAT8c4fagmhiwcfge4JcJaZ3mF0ZbqgEv8MU8Tr72Oqdc3ZQaj m5OA== 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=qZrJYoykwf3ME+oUDv+0yLazMZ6AQoVFLJRi5UWvX1A=; b=OZETrTa/lJr/50jSaeAxhc7A+90AWln9j8W/YBUGqnqSXSytfTdi13fVYn4omfqhrG IeJd9XQzjVj9oc9eDYuzc2cCh3xSzBqPvW66c1oOyf5QJcCBqb8DKX+9X3Q3wu1ct80M pe91qz5QKNuB4iJqfXUpM6MjeMw8ymqg0KpqYroJsfYG2IseUJ0lVakQGfuJHMJ165F5 KFWwtUAj9RNTbDaoulNHGL+nSKjS+8go2R4opiBo/7dI5hVNGqDTu+C9+KV4dHm3+SdF Oi7jpFufTfEn/KkMWNcYOE8nJ4jWCTmW4tG/sikDAsKSSwZhNG3/gmwB6W7Olq7hlzY+ pH+w== X-Gm-Message-State: AOAM533xW57uYCFK/hDHI1Mkunx3GybhKlKt4JR1iYQLYp2ucdJd5uR1 1vLAsZ07h4xCwVf7mJGB79+/rwpZtes= X-Google-Smtp-Source: ABdhPJxn7sX2l47l5kOcCGQPJVam+v4fS8qS+AVtiwyUaHJb7ktbnjQM68fyTT+8tk9J3HLgsGgM2Q== X-Received: by 2002:a05:6402:5206:: with SMTP id s6mr4502943edd.92.1613660079601; Thu, 18 Feb 2021 06:54:39 -0800 (PST) Original-Received: from [192.168.0.6] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id kv24sm2559706ejc.117.2021.02.18.06.54.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 Feb 2021 06:54:38 -0800 (PST) In-Reply-To: <83czwx5tfu.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:200264 Archived-At: 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.