Re: MemoryView missing from Python 2.4 and 2.6

[Yao Qi <qiyaoltc@gmail.com>]

"Wiederhake, Tim" <tim.wiederhake@intel.com> writes:

Hi Tim,

> 2) Refactor "gdb.Membuf" from python/py-inferior.c into its own file and use
> that. I don't like this idea too much because it is basically reinventing the
> wheel and gdb.Membuf is less versatile than build-in buffers, strings, etc.
>
> 3) Use the "new style buffer API" and limit GDB's support to Python >= 2.6.
> In this case we would have to limit the supported Python versions anyway so
> on the one hand there is not much reason to not throw out 2.6 as well. On the
> other hand, there still seem to be some Python 2.6 users.
>
> 4) Return a string in "gdb.BtraceInstruction.data ()". The instruction data can
> potentially contain null bytes which can cause issues for obvious reasons.

Before we think of them carefully, could you tell us how is the python
api "gdb.BtraceInstruction.data ()" affected by these options?  From a
GDB python api user's point of view, they use gdb.BtraceInstruction.data()
in their python code, if we take one of these options, and change it, do
they need to change their code too?  Once "gdb.BtraceInstruction.data()"
is released, it is harder to change it in the later releases.
Secondly, GDB can't be built with python 2.6 and 2.4, we still need to
think about whether python 2.4 and 2.6 is supported or not in GDB 8.0
release.

-- 
Yao (齐尧)