Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #13517

Re: Python3 -dbg packages

From Scott Talbert <swt@techie.net>
Newsgroups linux.debian.maint.python
Subject Re: Python3 -dbg packages
Date 2021-09-13 16:20 +0200
Message-ID <CWUYp-7nW-3@gated-at.bofh.it> (permalink)
References <ApEc2-7AK-31@gated-at.bofh.it> <CTddf-2Yt-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Python3 -dbg packages Matthias Klose <doko@debian.org> - 2020-07-06 20:40 +0200
  Re: Python3 -dbg packages Dmitry Shachnev <mitya57@debian.org> - 2020-07-07 10:50 +0200
  Re: Python3 -dbg packages Matthias Klose <doko@debian.org> - 2021-09-03 11:00 +0200
    Re: Python3 -dbg packages Scott Talbert <swt@techie.net> - 2021-09-13 16:20 +0200
      Re: Python3 -dbg packages Matthias Klose <doko@debian.org> - 2021-09-14 08:40 +0200
        Re: Python3 -dbg packages Matthias Klose <doko@debian.org> - 2021-09-15 12:50 +0200
          Re: Python3 -dbg packages Sandro Tosi <morph@debian.org> - 2021-09-15 15:30 +0200

csiph-web