From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 116882 invoked by alias); 21 Feb 2019 09:10:24 -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 116848 invoked by uid 89); 21 Feb 2019 09:10:24 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=1.5 required=5.0 tests=BAYES_40,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT autolearn=no version=3.3.2 spammy=2x, 2.x, UD:2.x, GDB's X-HELO: mircat.net Received: from mircat.net (HELO mircat.net) (81.9.105.50) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 21 Feb 2019 09:10:22 +0000 Received: from [84.47.189.78] (port=18179 helo=[172.27.105.179]) by mircat.net with esmtpsa (TLSv1.2:AES128-SHA:128) (Exim 4.85) (envelope-from ) id 1gwkMy-000Kag-Q7; Thu, 21 Feb 2019 12:10:16 +0300 Subject: Re: Proposal: Drop GDB support for Python versions < 2.6 To: =?UTF-8?B?QW5kcsOpIFDDtm5pdHo=?= , Kevin Buettner Cc: gdb@sourceware.org, Jan Vrany References: <20190220134506.13960235@f29-4.lan> <1e11ab8bf081211e6cd21f052244c834cd0f21e4.camel@fit.cvut.cz> <20190220151145.04ca21c2@f29-4.lan> <20190220232848.GB30732@klara.mpi.htwm.de> From: Dmitry Samersoff Openpgp: preference=signencrypt Message-ID: Date: Thu, 21 Feb 2019 09:10:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <20190220232848.GB30732@klara.mpi.htwm.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: dms@mircat.net X-Authenticated-As: dms X-SpamProbe: GOOD 0.0000107 1d59431295f45af3cfe60a3c3e80c1b2 X-IsSubscribed: yes X-SW-Source: 2019-02/txt/msg00035.txt.bz2 Andre, On 21.02.2019 2:28, André Pönitz wrote: > 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)? Yes. Lots of embedded staff is still on Python 2.x and maintaining separate version of Python just for gdb is problematic.