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, christian.heimes, georg.brandl, loewis, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner
Date 2012-08-09.06:24:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344493476.98.0.0307216309643.issue12834@psf.upfronthosting.co.za>
In-reply-to
Content
Removing 3.1, since its addition was apparently done by mistake.

Again, I wonder why this is marked release-critical. It's not a regression from previous versions, is it? Please use release-critical only if not making a release at a certain point in the future is better than making the release (despite all the advantages that the release otherwise might have). If you merely think that the issue is "really important" and "should not be forgotten", use "critical" or "high".
History
Date User Action Args
2012-08-09 06:24:37loewissetrecipients: + loewis, georg.brandl, ncoghlan, pitrou, vstinner, christian.heimes, benjamin.peterson, skrah, meador.inge, python-dev
2012-08-09 06:24:36loewissetmessageid: <1344493476.98.0.0307216309643.issue12834@psf.upfronthosting.co.za>
2012-08-09 06:24:36loewislinkissue12834 messages
2012-08-09 06:24:35loewiscreate