Hello,
On Wed, Jun 25, 2014 at 12:56:49PM -0700, Ben Longbons wrote:
> On Wed, Jun 25, 2014 at 3:58 AM, Matthias Klose wrote:
> > Am 25.06.2014 00:51, schrieb Ben Longbons:
> >> On Tue, Jun 24, 2014 at 3:08 PM, Matthias Klose wrote:
> >>> Are you aware of other pretty printers not
> >>> working
On 6/25/14, Matthias Klose wrote:
> Am 25.06.2014 02:51, schrieb Samuel Bronson:
>> * Guarantee that GDB will pull in the "six" package appropriate for
>> the Python it's built against (python-six or python3-six)
>
> this has nothing to do with 2/3. It is the responsibility of the package us
On Wed, Jun 25, 2014 at 3:58 AM, Matthias Klose wrote:
> Am 25.06.2014 00:51, schrieb Ben Longbons:
>> On Tue, Jun 24, 2014 at 3:08 PM, Matthias Klose wrote:
>>> Control: reopen -1
>>>
>>> so this is a very generic claim ("breaks everything") without giving any
>>> concrete package.
>>
>> It does
Am 25.06.2014 02:51, schrieb Samuel Bronson:
> * Guarantee that GDB will pull in the "six" package appropriate for
> the Python it's built against (python-six or python3-six)
this has nothing to do with 2/3. It is the responsibility of the package using
additional packages to declare these d
Hello,
2014-06-25 15:05 GMT+02:00 Matthias Klose :
> Am 25.06.2014 01:21, schrieb Hector Oron:
>> Can someone provide a list of pretty printers with some assesment
>> whether those work with Python 3 or not?
>
> searching the Contents file for -gdb.py should give you a pretty good idea.
>
> mono
Am 25.06.2014 01:21, schrieb Hector Oron:
> Hello,
>
> 2014-06-25 0:51 GMT+02:00 Ben Longbons :
>> On Tue, Jun 24, 2014 at 3:08 PM, Matthias Klose wrote:
>
>>> Are you aware of other pretty printers not
>>> working with python3?
>> From what I've seen, pretty printers that *do* work with python3
Am 25.06.2014 00:51, schrieb Ben Longbons:
> On Tue, Jun 24, 2014 at 3:08 PM, Matthias Klose wrote:
>> Control: reopen -1
>>
>> so this is a very generic claim ("breaks everything") without giving any
>> concrete package.
>
> It doesn't matter that it's not in a package.
>
> A debugger that can
Hmm, it seems to me we should discussing this on #727003, where you
asked for the switch to be done in the first place.
Matthias Klose writes:
> Control: reopen -1
>
> so this is a very generic claim ("breaks everything") without giving any
> concrete package.
Well, considering that the technic
Hello,
2014-06-25 0:51 GMT+02:00 Ben Longbons :
> On Tue, Jun 24, 2014 at 3:08 PM, Matthias Klose wrote:
>> Are you aware of other pretty printers not
>> working with python3?
> From what I've seen, pretty printers that *do* work with python3 are a
> very small minority.
Can someone provide a l
On Tue, Jun 24, 2014 at 3:08 PM, Matthias Klose wrote:
> Control: reopen -1
>
> so this is a very generic claim ("breaks everything") without giving any
> concrete package.
It doesn't matter that it's not in a package.
A debugger that can only be used to debug packages that are already
part of t
Control: reopen -1
so this is a very generic claim ("breaks everything") without giving any
concrete package.
(gdb) set python print-stack full
(gdb) info pretty-printer
global pretty-printers:
.*
bound
works here. You seem to be talking about a custom pretty printer, and still
using pyth
Package: gdb
Version: 7.6.2-1.1
Severity: important
Dear Maintainer,
A recent upload of gdb switched to python3 instead of python2.
Even if you really think a python3 gdb is useful, it should not be the
default, e.g. ship a gdb package using python2 and a gdb-python3 package
for people who don't
12 matches
Mail list logo
