Path: csiph.com!pasdenom.info!usenet.goja.nl.eu.org!3.eu.feeder.erje.net!feeder.erje.net!news.in-chemnitz.de!news.szaf.org!fu-berlin.de!bofh.it!news.nic.it!robomod From: =?UTF-8?B?w4lyaWM=?= Newsgroups: linux.debian.maint.python Subject: Re: Request to join the Debian Python Team Date: Sun, 12 Oct 2025 17:10:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Oct 12 15:00:24 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.9 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .netwok. - helo: .smtp-42a8.mail.infomaniak. - helo-domain: .infomaniak.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Greylist: delayed 375 seconds by postgrey-1.36 at bendel; Sun, 12 Oct 2025 15:00:11 UTC MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: fr Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Infomaniak-Routing: alpha X-Mailing-List: archive/latest/23302 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/5573f603-962a-4513-81f3-e7ac5fbba354@netwok.org Approved: robomod@news.nic.it Lines: 20 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sun, 12 Oct 2025 10:53:47 -0400 X-Original-Message-ID: <5573f603-962a-4513-81f3-e7ac5fbba354@netwok.org> X-Original-References: <68997721-87e9-43a8-8316-92d743778f55@netwok.org> Xref: csiph.com linux.debian.maint.python:17109 Le 09/10/2025 à 23:28, ben0i0d a écrit : > However, when I pulled the upstream code, I encountered > missing dependency errors related to |blurb| and |sphinx-build|. I’m not entirely sure why — > perhaps the Debian 3.14 source package includes some adjustments that I haven’t noticed. Yes, definitely. Debian adapts the build process to its needs. > So, I plan to submit this package later to fix the issue This still strikes me as the wrong approach. Upstream CPython developers add a news file for each non-trivial change, and the release process runs blurb to merge them into one big changelog file. Debian packaging is downstream from that process. The Debian Python maintainers don’t need blurb to build python3.14 (regular or free-threader flavour), so they patch the build system to not call it (or don’t use the make targets that call it). By the way: are you in touch with the Debian Python team? (core interpreter, not modules and applications) I wonder if they have plans to build a free-threaded package. It seems like a lot of work to do that on your own.