Path: csiph.com!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!bofh.it!news.nic.it!robomod From: Matthias Klose Newsgroups: linux.debian.maint.python Subject: Re: Python3 -dbg packages Date: Tue, 14 Sep 2021 08:40:02 +0200 Message-ID: References: X-Original-To: Scott Talbert X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Sep 14 06:37:04 2021 Old-Return-Path: X-Amavis-Spam-Status: No, score=-9.667 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, NICE_REPLY_A=-1.969, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 HELO_IP_IN_CL_SUBNET=-1.2 (check from: .debian. - helo: .einhorn-mail-out.in-berlin. - helo-domain: .in-berlin.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -2.7 Old-X-Envelope-From: doko@debian.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Mailing-List: archive/latest/19313 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/43823530-6740-8480-1c58-99e6a0ee1ee7@debian.org Approved: robomod@news.nic.it Lines: 48 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Tue, 14 Sep 2021 08:36:45 +0200 X-Original-Message-ID: <43823530-6740-8480-1c58-99e6a0ee1ee7@debian.org> X-Original-References: <2bb25f5a-6636-7d05-ed39-759e2bcee81d@debian.org> Xref: csiph.com linux.debian.maint.python:13518 On 9/13/21 4:02 PM, Scott Talbert wrote: > 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? yes, ideally, if there are dependencies on your -dbg in the archive, these should be removed first. Sorry, I didn't file these bug reports yet. Matthias