On Sun, May 29, 2016 at 1:59 AM, Hector Oron <hector.o...@gmail.com> wrote: > Please let me know your gdb-python2 use case, that'd be quite helpful.
I certainly prefer the python3 version most of the time - by this point, the infelicities of python3 are well understood and fewer in number than those of python2. However, remember that it is (to Debian) an RC bug to ship gdb python scripts that are not compatible with both python2 and python3, so being able to quickly test both is very important. And outside of Debian, I need to ship scripts that work with distros that don't have a python3 gdb. Yes, there's CI, but anything that doesn't get caught until that late takes a longer cycle to fix. Ideally, this *should* have been done for Jessie, but instead it got stuck only with the python2 version instead of allowing both. There *must* be at least one stable release that supports both; after that the python2 variant can be removed. -Ben
