From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 39048 invoked by alias); 21 Feb 2019 14:42:33 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 39030 invoked by uid 89); 21 Feb 2019 14:42:33 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,KAM_NUMSUBJECT,SPF_PASS autolearn=no version=3.3.2 spammy=drag, emacs, Emacs, Hx-languages-length:933 X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 21 Feb 2019 14:42:32 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:53368) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gwpYH-0003We-Cc; Thu, 21 Feb 2019 09:42:21 -0500 Received: from [176.228.60.248] (port=1992 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gwpYF-0007MA-OY; Thu, 21 Feb 2019 09:42:17 -0500 Date: Thu, 21 Feb 2019 14:42:00 -0000 Message-Id: <831s41gq49.fsf@gnu.org> From: Eli Zaretskii To: Kevin Buettner CC: gdb@sourceware.org In-reply-to: <20190220234610.6d8db6c7@f29-4.lan> (message from Kevin Buettner on Wed, 20 Feb 2019 23:46:10 -0700) Subject: Re: Proposal: Drop GDB support for Python versions < 2.6 References: <20190220134506.13960235@f29-4.lan> <20190221023904.GD14933@adacore.com> <83a7iphkjb.fsf@gnu.org> <20190220234610.6d8db6c7@f29-4.lan> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-IsSubscribed: yes X-SW-Source: 2019-02/txt/msg00043.txt.bz2 > Date: Wed, 20 Feb 2019 23:46:10 -0700 > From: Kevin Buettner > > > Dropping 2.6, let alone 2.7, would be a terrible nuisance for me. So > > I'm asking to keep that until they really put a drag on the GDB > > development (which doesn't seem to be the case now). > > That's fine. At the moment, there's no real reason to not continue to > (potentially) support 2.6. I say "potentially" because for some of us, > figuring out how to test against 2.6 is really hard. However, if you > continue to do regular builds of upstream gdb using Python 2.6, > it'll get tested. Yes, I build all the GDB versions with Python 2.6 and at least debugging Emacs some of the Python support is in constant use, as .gdbinit that ships with Emacs uses that. When we add a GDB feature whose support with Python 2.6 will be problematic, I won't object dropping 2.6. Thanks.