Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Matthias Klose Newsgroups: linux.debian.maint.python Subject: Re: Proposal IRC meeting DPT Date: Mon, 24 Jun 2024 10:50:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Jun 24 08:49:22 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.609 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, KHOP_HELO_FCRDNS=0.399, LDO_WHITELIST=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -2.7 X-Greylist: delayed 415 seconds by postgrey-1.36 at bendel; Mon, 24 Jun 2024 08:49:10 UTC Old-X-Envelope-From: doko@debian.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/22001 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/2c280a1d-3393-4133-a7d3-b468eccce4ac@debian.org Approved: robomod@news.nic.it Lines: 33 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 24 Jun 2024 10:42:03 +0200 X-Original-Message-ID: <2c280a1d-3393-4133-a7d3-b468eccce4ac@debian.org> X-Original-References: Xref: csiph.com linux.debian.maint.python:15965 On 22.06.24 00:06, Emmanuel Arias wrote: > Hi team, > > As the Louis-Philippe and Andreas response to my last mail [0] > I would like to propose a (regular?) IRC meeting to try to organize > the work inside the team. I would like to propose an IRC meeting > on 5 July, perhaps a good time could be around 12PM UTC and 4PM UTC? > That date and time work for you? Any different idea, time, hour is > welcome. > > I would like to propose the next points: > * List of packages that need to be removed [1] and how could we tackle > them. > * Effort needed to fix py3.12 or should be go directly to 3.13? The current status is tracked in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061188 it's now uploaded to unstable, and we'll start doing the binNMUs. Going directly to 3.13 is really not an option, Debian is relying on the upstream status of many packages, something that Debian cannot do on it's own. > * Check possible agenda for Python BoF for DebConf2024. 3.13 definitely is a topic for the Python BoF, especially when trying to default to 3.13 for the next Debian release. I will be there for the two last days of DebCamp, and will have time to work on any 3.13 preparations. I know, Stefano will be there as well, and hopefully not only involved with the video team ;p Matthias