This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Deprecating (and deleting) user-facing APIs [was Re: Why do functions objfpy_new and pspy_new exist?]
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Phil Muldoon <pmuldoon at redhat dot com>
- Cc: dje at google dot com, stanshebs at earthlink dot net, gdb-patches at sourceware dot org
- Date: Fri, 10 Oct 2014 10:50:54 +0300
- Subject: Re: Deprecating (and deleting) user-facing APIs [was Re: Why do functions objfpy_new and pspy_new exist?]
- Authentication-results: sourceware.org; auth=none
- References: <CADPb22Qj=z7GSBPohYAGRHaSUwx5W4VmSpM=bm_0yLp=yyY_pQ at mail dot gmail dot com> <54378CC0 dot 2060602 at redhat dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.