From: Phil Muldoon <pmuldoon@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dje@google.com, stanshebs@earthlink.net, gdb-patches@sourceware.org
Subject: Re: Deprecating (and deleting) user-facing APIs [was Re: Why do functions objfpy_new and pspy_new exist?]
Date: Fri, 10 Oct 2014 08:07:00 -0000 [thread overview]
Message-ID: <543793CE.9090109@redhat.com> (raw)
In-Reply-To: <834mvcbbxd.fsf@gnu.org>
On 10/10/14 08:50, Eli Zaretskii wrote:
>> Date: Fri, 10 Oct 2014 08:37:36 +0100
>> From: Phil Muldoon <pmuldoon@redhat.com>
>> CC: gdb-patches <gdb-patches@sourceware.org>
>>
>> So let me propose something. From GDB 8 on-wards, lets only support
>> Python 3.x. If this is too early, maybe 8.1 or 8.2. Anyway, we
>> message this consistently and continuously to the community. Document
>> it in all the right high traffic places. What do folks think?
>
> No, please don't unsupport Python 2.x, not yet. I'm still using
> Python 2.x based applications (e.g., bzr), and I'd like to avoid
> having 2 different versions of Python on the same machine, if
> possible.
I expect some push back from distro maintainers too. So this feedback
is all good; it might be that logistically for our users this might
not be possible at all. So that is what I would really love to hear -
thanks for letting me (and GDB) know.
However, 8.2 is quite far off. Do you know of any plans in the future
for your distro to support two Python versions or switch to 3? FWIW
later versions of Fedora supports both Pythons, and I think (though I
cannot find the link right now), have plans to move entirely to Python
3.
Anyway, thanks for the feedback. I do realize this might be a case of
sharing GDB Python developers' pain with others a little.
Cheers
Phil
next prev parent reply other threads:[~2014-10-10 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 18:07 Doug Evans
2014-10-10 7:38 ` Phil Muldoon
2014-10-10 7:51 ` Eli Zaretskii
2014-10-10 8:07 ` Phil Muldoon [this message]
2014-10-10 9:15 ` Eli Zaretskii
2014-10-10 16:35 ` Doug Evans
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=543793CE.9090109@redhat.com \
--to=pmuldoon@redhat.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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