Bug#890231: sagemath should use gdb, not gdb-python2, to be removed for buster

Ah, understood regarding gdb-python3. sagemath uses cysignals-CSI from the cysignals-tools package to print out a more detailed backtrace containing native, cython and python code, when tests fail. cysignals-CSI starts gdb and writes the contents of cysignals-CSI-helper.py [1] into gdb. That

Bug#890231: sagemath should use gdb, not gdb-python2, to be removed for buster

On 12.02.2018 15:41, Ximin Luo wrote: > Understood, but the entirety of sagemath is python2 at the moment and doesn't > support python3 (upstream is working on it). > > What's the timeframe for removal of gdb-python2 and will there be a > gdb-python3 alternative? gdb is built using python3. So

Bug#890231: sagemath should use gdb, not gdb-python2, to be removed for buster

Understood, but the entirety of sagemath is python2 at the moment and doesn't support python3 (upstream is working on it). What's the timeframe for removal of gdb-python2 and will there be a gdb-python3 alternative? X Matthias Klose: > Package: src:sagemath > Version: 8.2-3 > Severity: importa

Bug#890231: sagemath should use gdb, not gdb-python2, to be removed for buster

Package: src:sagemath Version: 8.2-3 Severity: important Tags: sid buster sagemath should use gdb, not gdb-python2, to be removed for buster. Please don't introduce new python2 (build) dependencies.