This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients benjamin.peterson, dmalcolm, georg.brandl, gregory.p.smith, loewis, pitrou, vstinner
Date 2012-06-26.21:39:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340746779.91.0.739402235419.issue12605@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2012-06-26 21:39:40loewissetrecipients: + loewis, georg.brandl, gregory.p.smith, pitrou, vstinner, benjamin.peterson, dmalcolm
2012-06-26 21:39:39loewissetmessageid: <1340746779.91.0.739402235419.issue12605@psf.upfronthosting.co.za>
2012-06-26 21:39:39loewislinkissue12605 messages
2012-06-26 21:39:37loewiscreate