Iustin Pop <ius...@debian.org> writes: > Reading > https://wiki.debian.org/Python/LibraryStyleGuide#Building_python_-dbg_packages, > there is some hints to this
The introduction of ‘foo-dbgsym’ automatic generated packages makes me quite sure those instructions are obsolete. But perhaps they are not? > but it's not clear that only automatic debug packages work for Python > packages. Would it make sense to update the wiki page and say "don't > migrate to dbgsym packages as Python needs debug extensions and not > only debug symbols"? Reading that reference again, I am not much wiser. It does not reference ‘foo-dbgsym’ packages so the reader doesn't know which instructions are to be followed. Could someone who understands *why* ‘foo-dbgsym’ is not sufficient, please update the wiki page to be explicit about what is special to Python and under what specific circumstances we still need ‘foo-dbg’ packages. -- \ “With Lisp or Forth, a master programmer has unlimited power | `\ and expressiveness. With Python, even a regular guy can reach | _o__) for the stars.” —Raymond Hettinger | Ben Finney