By default, GNUbg is built with an embedded Python language interpreter, allowing advanced scripting by calling evaluation and analysis functions from a general purpose programming language much more versatile than the basic CLI commands.
At this time, the version of the language that is used by default (by our Windows builds and, as far as I know, by all Linux distributions and BSD-style ports) is Python 2. Python 3 has been supported for some time though and GNUbg can already be built with it instead. Python 2 support by its developers will stop at the end of the year. This version will certainly remain available in Linux distributions and in the mingw toolkit used for Windows builds, but we certainly will switch to Python 3 at some time. I'd be interested in feedback from : - people who use Python with GNUbg. Would you be rather reluctant to the change ? Or are you familiar enough with both versions of the language and already use code compatible with either one with little or no modifications ? Or are you already using a self-built, Python3-enabled, GNUbg ? - package maintainers for Linux distributions. What do you intend to do for GNUbg ? Does your distribution have general recommendations or policies about which Python version to use ? _______________________________________________ Bug-gnubg mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-gnubg
