From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17119 invoked by alias); 21 Feb 2019 06:39:20 -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 17093 invoked by uid 89); 21 Feb 2019 06:39:20 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,KAM_NUMSUBJECT,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=HTo:U*gdb, 2x, 2.x, UD:2.x X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 21 Feb 2019 06:39:19 +0000 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 27C48368E7; Thu, 21 Feb 2019 06:39:17 +0000 (UTC) Received: from f29-4.lan (ovpn-117-11.phx2.redhat.com [10.3.117.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id EA6D55D9D5; Thu, 21 Feb 2019 06:39:16 +0000 (UTC) Date: Thu, 21 Feb 2019 06:39:00 -0000 From: Kevin Buettner To: gdb@sourceware.org Cc: =?ISO-8859-1?Q?Andr=E9_P=F6nitz?= Subject: Re: Proposal: Drop GDB support for Python versions < 2.6 Message-ID: <20190220233915.30b52f4c@f29-4.lan> In-Reply-To: <20190220232848.GB30732@klara.mpi.htwm.de> References: <20190220134506.13960235@f29-4.lan> <1e11ab8bf081211e6cd21f052244c834cd0f21e4.camel@fit.cvut.cz> <20190220151145.04ca21c2@f29-4.lan> <20190220232848.GB30732@klara.mpi.htwm.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2019-02/txt/msg00033.txt.bz2 On Thu, 21 Feb 2019 00:28:48 +0100 Andr=C3=A9 P=C3=B6nitz wrote: > On Wed, Feb 20, 2019 at 03:11:45PM -0700, Kevin Buettner wrote: > > On Wed, 20 Feb 2019 21:44:39 +0000 > > Jan Vrany wrote: > >=20=20=20 > > > Actually, I'd even be fine with more radical move, dropping support=20 > > > for 2.x altogether. Python 2.7 support will end in less a year=20 > > > from now anyway.=20=20=20 > >=20 > > I'm not ready to drop support for all of 2.X.=20=20 >=20 > Out of curiosity: Why? >=20 > I.e. are there realistic scenarios where people actively use GDB's Python > interface (in this context here I am tempted to call it a fairly "recent" > addition to GDB, the first commit seems to be dated Aug 6, 2008), but are > not able to use it with Python 3.x (3.0 released on Dec 3, also 2008)? I think so. See Eli's reply in this thread. When I build GDB on Fedora, I get a gdb enabled for python 2.7 unless I take measures (via --with-python=3D/usr/bin/python3) to use python 3.X instead. I just checked three recent linux distro releases: Mint 19.1, Debian 9.8, a= nd Fedora 29. For each of them, running "python --version" shows that they're all Python 2.7.X. Python 3 is often available, but you have to use the python3 command to use it. Checking my CentOS 7.6 box, I find that Python 2.7.5 is installed, but Python 3 is not. However, I see that I could install some version of Python 3 if I needed it. (I'm not using this machine for development.) I think we can drop Python 2.7 (and lower) sometime after the major Linux distributions start defaulting to python 3.X for the "python" command. Kevin