From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 49325 invoked by alias); 20 Feb 2019 22:05:01 -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 49182 invoked by uid 89); 20 Feb 2019 22:05:00 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=0.5 required=5.0 tests=BAYES_40,KAM_NUMSUBJECT,SPF_PASS autolearn=no version=3.3.2 spammy=HTo:U*gdb, H*Ad:U*gdb, massive, 2x 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; Wed, 20 Feb 2019 22:04:58 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:39983) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gwZz5-00080e-2M for gdb@sourceware.org; Wed, 20 Feb 2019 17:04:55 -0500 Received: from [50.226.24.42] (port=40450 helo=pdslaptop) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gwZz5-0002n6-02 for gdb@sourceware.org; Wed, 20 Feb 2019 17:04:55 -0500 Message-ID: <4df03e9038ffc301b771ad1249138cecf1083236.camel@gnu.org> Subject: Re: Proposal: Drop GDB support for Python versions < 2.6 From: Paul Smith Reply-To: psmith@gnu.org To: gdb@sourceware.org Date: Wed, 20 Feb 2019 22:05:00 -0000 In-Reply-To: <1e11ab8bf081211e6cd21f052244c834cd0f21e4.camel@fit.cvut.cz> References: <20190220134506.13960235@f29-4.lan> <1e11ab8bf081211e6cd21f052244c834cd0f21e4.camel@fit.cvut.cz> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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/msg00024.txt.bz2 On Wed, 2019-02-20 at 21:44 +0000, Jan Vrany wrote: > Actually, I'd even be fine with more radical move, dropping support > for 2.x altogether. Python 2.7 support will end in less a year > from now anyway. I expected someone to say this :). I'm well aware of the EOL pan for Python 2.7, obviously. However, I cannot begin to guess when we'll stop using it internally due to the massive (and 100% unproductive) overhead involved with transitioning to Python 3. We only use Python (and GDB!) internally, and we build it ourselves we don't use a version that comes with our distribution, so it doesn't really matter to us how well supported it is externally. So, I would be unhappy if support for Python 2.7 were dropped. However, when it becomes a big burden for GDB devs to support it I guess we'll have to do something else (build Python 3 just for GDB?) Again, just speaking as a user, not a GDB developer.