From: <Paul_Koning@Dell.com>
To: <jan.kratochvil@redhat.com>
Cc: <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [patchv2] Fix Python 3 build error on 32-bit hosts
Date: Wed, 04 Feb 2015 21:06:00 -0000 [thread overview]
Message-ID: <996919F0-2682-4D3A-9064-17FEB8F73D7B@dell.com> (raw)
In-Reply-To: <20150204192028.GA12310@host1.jankratochvil.net>
> On Feb 4, 2015, at 2:20 PM, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
>
> On Wed, 04 Feb 2015 19:58:18 +0100, Pedro Alves wrote:
>> I agree with Paul here. I think checking Python version is sufficient.
>
> I should point out that version checking is error prone to distro backports.
That’s true in many cases. But here we’re dealing with a documented API difference, and the definition explicitly states that the change is associated with a particular Python version (core version, not distro).
paul
prev parent reply other threads:[~2015-02-04 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 17:43 [patch] " Jan Kratochvil
2015-02-04 18:39 ` Paul_Koning
2015-02-04 18:58 ` Pedro Alves
2015-02-04 19:08 ` Pedro Alves
2015-02-04 19:20 ` [patchv2] " Jan Kratochvil
2015-02-04 19:27 ` Pedro Alves
2015-02-04 19:34 ` [commit] " Jan Kratochvil
2015-02-04 19:42 ` Pedro Alves
2015-02-04 19:51 ` Phil Muldoon
2015-02-04 21:06 ` Paul_Koning [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=996919F0-2682-4D3A-9064-17FEB8F73D7B@dell.com \
--to=paul_koning@dell.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).