| Message ID | 58a0c85ad35db14c9fed7d5791b43d30882e13bf.1713169547.git.mail@cbaines.net |
|---|---|
| State | New |
| Headers | show |
| Series | [bug#70393] gnu: python-pydevd: Use gdb/pinned. | expand |
Hi! Christopher Baines <mail@cbaines.net> skribis: > To allow gdb to be updated more easily. > > * gnu/packages/python-xyz.scm (python-pydevd)[inputs]: Use gdb/pinned. > > Change-Id: Icf417f89933bc190bf4c0d869c199cfe50d463ef [...] > - (inputs (list coreutils gdb procps)) > + (inputs (list coreutils gdb/pinned procps)) > (home-page "https://github.com/fabioz/PyDev.Debugger/") > (synopsis "Python debugger") If PyDev uses GDB, then it’ll be stuck with an older version of GDB? Maybe that’s OK? (I know nothing about PyDev and how it uses GDB so I can’t really judge whether it’s OK.) Ludo’.
Ludovic Courtès <ludo@gnu.org> writes: > Hi! > > Christopher Baines <mail@cbaines.net> skribis: > >> To allow gdb to be updated more easily. >> >> * gnu/packages/python-xyz.scm (python-pydevd)[inputs]: Use gdb/pinned. >> >> Change-Id: Icf417f89933bc190bf4c0d869c199cfe50d463ef > > [...] > >> - (inputs (list coreutils gdb procps)) >> + (inputs (list coreutils gdb/pinned procps)) >> (home-page "https://github.com/fabioz/PyDev.Debugger/") >> (synopsis "Python debugger") > > If PyDev uses GDB, then it’ll be stuck with an older version of GDB? > Maybe that’s OK? (I know nothing about PyDev and how it uses GDB so I > can’t really judge whether it’s OK.) I don't really know either, but at least this will allow updating gdb without rebuilding a bunch of Python things.
Hi Chris, > > If PyDev uses GDB, then it’ll be stuck with an older version of GDB? > > Maybe that’s OK? (I know nothing about PyDev and how it uses GDB so I > > can’t really judge whether it’s OK.) > > I don't really know either, but at least this will allow updating gdb > without rebuilding a bunch of Python things. I don’t see anything that would prevent pydevd running on a pinned/older GDB version. We might want to verify when we update python-pydevd, but right now it just attaches to the process and injects a shared object – that’s all. So, LGTM. Lars
Hi, Lars-Dominik Braun <lars@6xq.net> skribis: >> > If PyDev uses GDB, then it’ll be stuck with an older version of GDB? >> > Maybe that’s OK? (I know nothing about PyDev and how it uses GDB so I >> > can’t really judge whether it’s OK.) >> >> I don't really know either, but at least this will allow updating gdb >> without rebuilding a bunch of Python things. > > I don’t see anything that would prevent pydevd running on a pinned/older > GDB version. We might want to verify when we update python-pydevd, but > right now it just attaches to the process and injects a shared object > – that’s all. So, LGTM. OK, thanks for checking. Go for it, Chris! Ludo’.
diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm index 92566abfed..a19422aa4a 100644 --- a/gnu/packages/python-xyz.scm +++ b/gnu/packages/python-xyz.scm @@ -16471,7 +16471,7 @@ (define-public python-pydevd python-pytest-xdist python-trio python-untangle)) - (inputs (list coreutils gdb procps)) + (inputs (list coreutils gdb/pinned procps)) (home-page "https://github.com/fabioz/PyDev.Debugger/") (synopsis "Python debugger") (description "PyDev.Debugger is a capable Python debugger used in PyDev