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 georg.brandl
Recipients asvetlov, chris.jerdonek, georg.brandl, gregory.p.smith, pitrou, r.david.murray
Date 2012-08-19.10:59:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The main question: can be fix applied to 3.3 or it can wait for 3.4?
> 3.2 has the same problem BTW.

I don't see any fix attached :)

If it is a bug, it can be fixed before 3.3rc1, no need for release blocker status.
Date User Action Args
2012-08-19 11:00:10georg.brandlsetrecipients: + georg.brandl, gregory.p.smith, pitrou, r.david.murray, asvetlov, chris.jerdonek
2012-08-19 11:00:10georg.brandlsetmessageid: <>
2012-08-19 10:59:49georg.brandllinkissue12623 messages
2012-08-19 10:59:49georg.brandlcreate