From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eliz@gnu.org>
Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10])
 by sourceware.org (Postfix) with ESMTPS id AB89939878F8
 for <gdb@sourceware.org>; Thu, 17 Sep 2020 18:02:56 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org AB89939878F8
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=gnu.org
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=eliz@gnu.org
Received: from fencepost.gnu.org ([2001:470:142:3::e]:42422)
 by eggs.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <eliz@gnu.org>)
 id 1kIyFD-00064z-Sv; Thu, 17 Sep 2020 14:02:55 -0400
Received: from [176.228.60.248] (port=3982 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <eliz@gnu.org>)
 id 1kIyF9-0006cf-1O; Thu, 17 Sep 2020 14:02:55 -0400
Date: Thu, 17 Sep 2020 21:03:02 +0300
Message-Id: <83o8m45lih.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: tom@tromey.com, paulkoning@comcast.net, gdb@sourceware.org
In-Reply-To: <20200917174940.GB30765@adacore.com> (message from Joel Brobecker
 on Thu, 17 Sep 2020 10:49:40 -0700)
Subject: Re: Proposal to remove Python 2 support
References: <87sgbiahur.fsf@tromey.com>
 <3415E02F-C35C-4C72-8C9A-C141E024F3AC@comcast.net>
 <1600210499.574691995@f12.my.com>
 <20200916130013.GC5797@adacore.com>
 <20200916135312.GB3030@embecosm.com>
 <20200916152329.GD5797@adacore.com>
 <20200916153400.GC3030@embecosm.com> <87lfh872n6.fsf@tromey.com>
 <20200917174940.GB30765@adacore.com>
X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: gdb@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb mailing list <gdb.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb>,
 <mailto:gdb-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb>,
 <mailto:gdb-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Sep 2020 18:02:57 -0000

> Date: Thu, 17 Sep 2020 10:49:40 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Paul Koning <paulkoning@comcast.net>, gdb@sourceware.org
> 
> I agree we should be very careful about that, and keep things clear
> for the users. One the one hand, a full on/off switch, with a clear
> message "your GDB was configured without Python support" is simple
> for users to understand. On the other hand, having the API itself
> depend on what version of Python GDB was built with would make things
> pretty confusing, in my opinion.

But that kind of thing is inevitable when one relies on external
libraries for some of our features.  For example, suppose that the
source-highlight package learns to highlight sources better -- these
improvements will only available to users if they upgrade their
installed source-highlight library before building GDB.  Granted,
these differences are smaller than entire commands or features
missing, but they still do exist, and always will.

So I don't think we should be too worried about this.