From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id 9F52B3858C60 for ; Mon, 10 Jan 2022 16:39:11 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 9F52B3858C60 Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 20AGd4Y7021575 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 10 Jan 2022 11:39:09 -0500 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 20AGd4Y7021575 Received: from [10.0.0.11] (192-222-157-6.qc.cable.ebox.net [192.222.157.6]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 3EBCA1EA69; Mon, 10 Jan 2022 11:39:04 -0500 (EST) Message-ID: Date: Mon, 10 Jan 2022 11:39:02 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: [PATCH 1/3] gdb/python: remove Python 2 support Content-Language: en-US To: Joel Brobecker Cc: Andrew Burgess via Gdb-patches References: <20220107152921.2858909-1-simon.marchi@polymtl.ca> <20220107174405.GC622389@redhat.com> From: Simon Marchi In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Mon, 10 Jan 2022 16:39:04 +0000 X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2022 16:39:16 -0000 On 2022-01-09 21:59, Joel Brobecker wrote: >> Personally, I would also prefer merging sooner than later, just because >> once it's done I can stop worrying about it. But I am also not in a >> hurry. What finally triggered me to do this was the review of >> Andrew's patch, I don't know if that is urgent or not. >> >> Joel, I don't think that the problem is the time we leave to downstream >> users who might be impacted, but how we reach them. I like the idea of >> the NEWS entry to give a heads up, because it might be the only way we >> have to communicate with some downstream users. Oh, and we could also >> make it so GDB shows a warning at startup if it's built with Python 2, >> saying that Python 2 support will be removed in the next version. That >> has maybe more chances of being seen. >> >> If drop support in GDB 12, we don't have a chance to warn users (unless >> we add that warning to GDB 11.2...). We could always send an email on >> the mailing lists, but that probably doesn't have as much reach. >> >> So, if there is no particular rush, I am leaning towards aiming for GDB >> 13. > > If you do not mind, then, OK for me as well. But just in the spirit of > exploring all our options: What about adding a warning in the 11.2 NEWS? > We create a PR, add news entry, and the change is in both the NEWS and > the announcement I'm sending to everyone. We can also add a dedicated > NEWS entry on GDB's web page. Even though it would be possible to add the deprecation notice in 11.2, I don't think we should. I see Python 2 getting the "will be removed in next release" a bit like a new feature, and we should not introduce it in a bugfix release. Simon