From: Yao Qi <qiyaoltc@gmail.com>
To: "Wiederhake, Tim" <tim.wiederhake@intel.com>
Cc: "Jose E. Marchesi" <jose.marchesi@oracle.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: MemoryView missing from Python 2.4 and 2.6
Date: Mon, 20 Mar 2017 22:44:00 -0000 [thread overview]
Message-ID: <CAH=s-PNmW4iu85DT1J7Kiw_U0K5gM=5OdYPqgTBtVwyPY6r8Yw@mail.gmail.com> (raw)
In-Reply-To: <861stse2uf.fsf@gmail.com>
On Mon, Mar 20, 2017 at 9:04 AM, Yao Qi <qiyaoltc@gmail.com> wrote:
> "Wiederhake, Tim" <tim.wiederhake@intel.com> writes:
>
> This patch is OK to go in, with the fix to the doc.
As Eli comment
https://sourceware.org/ml/gdb-patches/2017-03/msg00344.html
"Python 3" is correct. I withdraw my comment below. Your patch
is OK to go in.
>
>> @defvar BtraceInstruction.data
>> A buffer with the raw instruction data. May be @code{None} if the
>> -instruction is a gap.
>> +instruction is a gap. In Python 3, the return value is a @code{memoryview}
>> +object.
>> @end defvar
>
> s/Python 3/@code{Python} 3/
>
--
Yao (齐尧)
prev parent reply other threads:[~2017-03-20 22:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 16:48 Jose E. Marchesi
2017-02-23 17:06 ` Jose E. Marchesi
2017-02-23 22:59 ` Yao Qi
2017-02-24 10:37 ` Wiederhake, Tim
2017-02-24 16:06 ` Yao Qi
2017-02-24 16:14 ` Paul.Koning
2017-02-28 10:53 ` Wiederhake, Tim
2017-02-28 12:51 ` Jose E. Marchesi
2017-03-07 0:21 ` Joel Brobecker
2017-03-07 13:38 ` Wiederhake, Tim
2017-03-07 15:27 ` Joel Brobecker
2017-03-03 10:21 ` Yao Qi
2017-03-06 8:56 ` Wiederhake, Tim
2017-03-07 10:32 ` Yao Qi
2017-03-07 17:18 ` Wiederhake, Tim
2017-03-17 15:59 ` Yao Qi
2017-03-17 16:39 ` Jose E. Marchesi
2017-03-20 9:04 ` Yao Qi
2017-03-20 22:44 ` Yao Qi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH=s-PNmW4iu85DT1J7Kiw_U0K5gM=5OdYPqgTBtVwyPY6r8Yw@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.com \
--cc=tim.wiederhake@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox