Path: csiph.com!1.us.feeder.erje.net!3.us.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!news.uzoreto.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Thomas Goirand Newsgroups: linux.debian.maint.python Subject: Re: Python 3.11 for bookworm? Date: Thu, 15 Dec 2022 16:20:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Dec 15 15:10:26 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-110.025 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.515, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Content-Language: en-US Organization: Debian Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Debian-User: zigo X-Mailing-List: archive/latest/20595 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/a8f03680-8b1a-bd01-1575-31ec8ec3ed76@debian.org Approved: robomod@news.nic.it Lines: 34 Sender: robomod@news.nic.it X-Original-Cc: Graham Inggs X-Original-Date: Thu, 15 Dec 2022 16:10:05 +0100 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.python:14729 On 12/13/22 13:34, Julian Gilbey wrote: > Hi Graham, > > On Mon, Dec 12, 2022 at 11:51:11PM +0000, Graham Inggs wrote: >> Dear Python Team >> >> Looking at the current state of the 'adding Python 3.11 as a supported >> version' transition [1], the tracker [2] shows only 12 red packages >> (excluding unknowns and packages not in testing) remaining, copied >> below for reference. >> [...] > > If Python 3.11 is the default, then it is highly likely that Spyder > will not be included: debugpy, which is a dependency of Spyder and > python3-ipykernel (and lots of things that depend on that) seems to > require major work upstream to make it fully compatible with Python > 3.11. This is work in progress, but I don't know whether it will be > ready in time for the freeze. At the moment, I have worked around > this problem by just skipping the failing tests, but that is far from > an ideal solution. > > Best wishes, > > Julian Hi Julian, It's probably ok if it's a *TEMPORARY* solution until upstream fixes everything in time for the release (which is months after the freeze). The question is: do you believe this may happen for let's say next March? Cheers, Thomas Goirand (zigo)