From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) by sourceware.org (Postfix) with ESMTPS id 33C3C3891C11 for ; Mon, 10 Jan 2022 02:59:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 33C3C3891C11 Received: by mail-wm1-x335.google.com with SMTP id p18so1049631wmg.4 for ; Sun, 09 Jan 2022 18:59:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=zgDlQv4yoMbeYKd7qckmcxlMrXgksvKWxTF8KtNEcaU=; b=SY+eeZ4Y4FE3+wLW+iKcZK0TF4kj/3OIInB9WJPiTnlbbGwwvW61dCaucHc9iInL9U tbnoKmNWGOBa/8jnO/zK55mtaR7yVIBJr7fTrtlr31dFAv7nOPA9x0Uwquc8SJIYh5nw v92CJ6ARL1ATxCl0Cxebb68pesJC/2Gutdk6ajYfq+d2bcIhgd9/2CRMNy6cXgrWJhoG 2hSLyZ4509X+7aVfpKVKjhSB+2OLkOuGhgPuxad3QGqQWtqqSugyefiobFPZSI8zHQgo Nus/xtH9PydN7XD+hPWh7JZIjZSlwD8pkaJGDHk3Mt+VuZp/i+Vsy8cX2uHHNJoQaoAo vrRg== X-Gm-Message-State: AOAM532JM17qZEplDj7xlByuzfmSFr1uZ1q0aQ2cten5fLyv9GzRv+cY CTUmkLqhXlabGLBNNaUr6RovT3x6sfv9 X-Google-Smtp-Source: ABdhPJxrdlEeaTPv6Nv6SFMbC8H4l1bdyC2LT323WZb7YFhSPmF8D7ccNs5FcUICdAf9dG4LMa8hmA== X-Received: by 2002:a7b:c30e:: with SMTP id k14mr20276347wmj.74.1641783553320; Sun, 09 Jan 2022 18:59:13 -0800 (PST) Received: from takamaka.home (lfbn-reu-1-342-220.w92-130.abo.wanadoo.fr. [92.130.175.220]) by smtp.gmail.com with ESMTPSA id r13sm5485890wmq.28.2022.01.09.18.59.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 09 Jan 2022 18:59:12 -0800 (PST) Received: by takamaka.home (Postfix, from userid 1000) id 68C75A4A59; Mon, 10 Jan 2022 06:59:10 +0400 (+04) Date: Mon, 10 Jan 2022 06:59:10 +0400 From: Joel Brobecker To: Simon Marchi Cc: Joel Brobecker , Andrew Burgess via Gdb-patches Subject: Re: [PATCH 1/3] gdb/python: remove Python 2 support Message-ID: References: <20220107152921.2858909-1-simon.marchi@polymtl.ca> <20220107174405.GC622389@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, 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 02:59:15 -0000 > 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. -- Joel