From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: tom@tromey.com (Tom Tromey)
Cc: kevinb@redhat.com (Kevin Buettner),
gdb-patches@sourceware.org, tom@tromey.com (Tom Tromey)
Subject: Re: [PATCH 2/4] Define gdb.Value(bufobj, type) constructor
Date: Tue, 19 Feb 2019 15:28:00 -0000 [thread overview]
Message-ID: <20190219152812.EED6CD8029F@oc3748833570.ibm.com> (raw)
In-Reply-To: <87wolvu7pk.fsf@tromey.com> from "Tom Tromey" at Feb 19, 2019 08:19:19 AM
Tom Tromey wrote:
> >>>>> "Kevin" =3D=3D Kevin Buettner <kevinb@redhat.com> writes:
>
> >> However, this seems like a decision to make consciously.
> >> I'm not completely sure how to proceed, though one idea might be to find
> >> the most recent Python 2.[456] compatibility patch and then asking the
> >> author whether this support is still relevant.
>
> Kevin> I didn't know of that compatibility patch, though I'll try to track =
> it
> Kevin> down. (A pointer would be appreciated if you have one handy.)
>
> I just recall it happening from time to time. Using:
>
> git log --grep 'Python 2\.[4-6]'
So I've been running an SPU build bot on RHEL 5, which still has Python 2.4
as system version. Those patches were from when I noticed build breaks
because of that.
However, a while back I switched my build bot to use a private Python 2.7
instead of the system Python 2.4, so I guess at this point I'm not even
noticing any 2.4 related issues. As far as I'm concerned, I'd be fine
with removing compatibility with older Python versions ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2019-02-19 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190218075816.6f67f3d9@f29-4.lan>
2019-02-18 15:03 ` [PATCH 1/4] Define unique_ptr specialization for Py_buffer Kevin Buettner
2019-02-18 15:06 ` [PATCH 2/4] Define gdb.Value(bufobj, type) constructor Kevin Buettner
2019-02-18 22:46 ` Tom Tromey
2019-02-19 0:57 ` Kevin Buettner
2019-02-19 15:19 ` Tom Tromey
2019-02-19 15:28 ` Ulrich Weigand [this message]
2019-02-19 2:41 ` Simon Marchi
2019-02-18 15:07 ` [PATCH 3/4] Add tests for " Kevin Buettner
2019-02-19 2:46 ` Simon Marchi
2019-02-18 15:09 ` [PATCH 4/4] Document two argument form of gdb.Value constructor Kevin Buettner
2019-02-18 16:13 ` Eli Zaretskii
2019-02-18 17:25 ` Kevin Buettner
2019-02-18 17:45 ` Eli Zaretskii
2019-02-19 2:48 ` [PATCH 0/4] Define gdb.Value(val, type) constructor Simon Marchi
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=20190219152812.EED6CD8029F@oc3748833570.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=tom@tromey.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