From: <Paul.Koning@dell.com>
To: <brobecker@adacore.com>
Cc: <pmuldoon@redhat.com>, <gdb@sourceware.org>
Subject: Re: GDB fails to build with Python 3.7
Date: Thu, 31 May 2018 17:28:00 -0000 [thread overview]
Message-ID: <ADFEFF18-034E-4C26-A56E-D9D6EA905081@dell.com> (raw)
In-Reply-To: <20180530222629.642gog77pan2uzm5@adacore.com>
> On May 30, 2018, at 6:26 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>
> From what I can tell, this was was introduced when you added
> Python 3.x support, back in 2012:
>
> commit 9a27f2c60d760a95a27e336750f26f69f91dd156
> Date: Wed Dec 12 16:47:30 2012 +0000
> Subject: Add support for Python 3
>
> Do you remember why you added that _PyImport_FixupBuiltin call?
I just submitted a proposed patch for this. It's pretty easy, I'm not
sure how I missed it originally. Possible the documentation has
improved in the meantime.
paul
next parent reply other threads:[~2018-05-31 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5e55cd3c-7ccd-4cce-5297-ddddadf91975@redhat.com>
[not found] ` <20180530222629.642gog77pan2uzm5@adacore.com>
2018-05-31 17:28 ` Paul.Koning [this message]
2018-05-29 11:37 Phil Muldoon
2018-05-29 12:11 ` Paul.Koning
2018-05-29 12:55 ` Phil Muldoon
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=ADFEFF18-034E-4C26-A56E-D9D6EA905081@dell.com \
--to=paul.koning@dell.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=pmuldoon@redhat.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