Path: csiph.com!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!bofh.it!news.nic.it!robomod From: Scott Talbert Newsgroups: linux.debian.maint.python Subject: Re: Python3 -dbg packages Date: Mon, 13 Sep 2021 16:20:01 +0200 Message-ID: References: X-Original-To: Matthias Klose X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Sep 13 14:10:28 2021 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.2 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] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -4.6 X-Greylist: delayed 454 seconds by postgrey-1.36 at bendel; Mon, 13 Sep 2021 14:10:15 UTC X-X-Sender: talbert@bear.techie.net User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Mailing-List: archive/latest/19311 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/alpine.DEB.2.22.394.2109131000430.142759@bear.techie.net Approved: robomod@news.nic.it Lines: 44 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Mon, 13 Sep 2021 10:02:36 -0400 (EDT) X-Original-Message-ID: X-Original-References: <2bb25f5a-6636-7d05-ed39-759e2bcee81d@debian.org> Xref: csiph.com linux.debian.maint.python:13517 On Fri, 3 Sep 2021, Matthias Klose wrote: >> Python 3.8 upstream now has a common ABI for normal and debug extension builds, >> so it is technically possible to load a debug extension in the normal >> interpreter, or to load a normal extension in the debug interpreter. In Debian, >> debug extensions are shipped with a different name, and only loaded by the >> corresponding interpreter. We could change / simply the current setup, but I >> first wanted to know how many people are still using the debug builds. The >> reason for the separate debug builds allowed debugging of stuff in modules >> further down the Python stack, without having to rebuild the whole stack. There >> are several solutions how to simplify the packaging, I'm not sure how much the >> dbg extensions are still used ... There are several scenarios: >> >> - Keep the current setup (-dbg packages need to be available to >> run them). >> >> - Allow the debug interpreter to load normal debug extensions (but >> load a debug extension if it's available by default). That would >> allow building debug extensions without having debug extensions >> built for all it's dependencies, maybe requiring changes in the >> dependencies of a package. >> >> - Stop building debug extensions, and telling developers to >> build extensions in debug mode, if they need them. That would >> probably be inline with everything else shipped in Debian. >> >> - Stop building debug extensions, and also stop building the Python >> debug interpreter. You would need to rebuild the interpreter >> itself to have meaningful debug sessions. I'm not preferring >> this solution. >> >> I'm currently tending to implement the second scenario, but if people think that >> having the -dbg packages available is still useful, then also opt for the third >> option. > > Let's address this before we start adding Python 3.10 as a supported Python3 > version. Starting with the third option. I'll file bug reports for the > following packages: Just to confirm on this: if we currently have a python module that builds a -dbg package, we can now drop this in favor of the automatically generated -dbgsym package for debugging? Scott