Martin v. Löwis <mar...@v.loewis.de> added the comment: I'm +1 on adding this in general, +0 on adding this to 3.3, and -0 on adding it to 2.7 right away.
I agree that the usual reasoning against new features doesn't apply here, since it's not a new Python (language or library) feature. However, one concern is that it is a large change, and I predict that it will introduce some breakage regardless of what amount of code review goes into it. If the breakage can be detected during the betas, fine, but we need to consider that it may cause breakage of the entire python-gdb feature for some people after the release (which probably wouldn't be that terrible). Hence the +0 for 3.3. For 2.7, it should only be added if it has survived in a prerelease branch for some time, hence the -0. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12605> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
