This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Deprecating (and deleting) user-facing APIs [was Re: Why do functions objfpy_new and pspy_new exist?]


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]