➜

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 barry
Recipients Arfrever, barry, benjamin.peterson, bethard, chris.jerdonek, georg.brandl, r.david.murray
Date 2012-09-11.19:15:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20120911151457.26aa52ec@resist.wooz.org>
In-reply-to <1347390013.08.0.0244019835572.issue15906@psf.upfronthosting.co.za>
Content 
On Sep 11, 2012, at 07:00 PM, R. David Murray wrote:

>To repeat: there is no change to be made for 3.3.  3.3.0 will go out the door
>with the pre-12776 behavior.  So any backward compatibility concerns that
>apply to 2.7 and 3.2 also apply to 3.3.  Thus I suggest we restore the string
>check, and consider an enhancement patch at more leisure for 3.4.

Okay, I missed that Georg has a separate branch for the 3.3.0 release, so we
don't have to worry about it there.  But yes, 2.7, 3.2, and 3.3.1 must be
fixed.
History
Date User Action Args
2012-09-11 19:15:04barrysetrecipients: + barry, georg.brandl, bethard, benjamin.peterson, Arfrever, r.david.murray, chris.jerdonek
2012-09-11 19:15:01barrylinkissue15906 messages
2012-09-11 19:15:01barrycreate