Vincent Bernat <> writes:

> The page seems up-to-date

It makes no reference to why ‘foo-dbgsym’ is not enough, so the reader
doesn't have any guidance on which practice overrules the other.

> and already explains why Python is different (presence of a debug
> interpreter)

As I said, that doesn't explain it.

Please consider that someone reading those instructions may have no more
sophisticated idea of debug symbol packages than “I heard that they are
done automatically now, so I'll just rely on that”.

So this:

> and that the -dbg package contains the symbols for the regular
> extensions as well as the unstripped extensions for the debug
> interpreter.

doesn't address the confusion, I think.

 \        “If you go parachuting, and your parachute doesn't open, and |
  `\        you friends are all watching you fall, I think a funny gag |
_o__)             would be to pretend you were swimming.” —Jack Handey |
Ben Finney

Reply via email to