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 gvanrossum
Recipients benjamin.peterson, giampaolo.rodola, gvanrossum, ncoghlan, pitrou, python-dev, richard.kiss, vstinner, yselivanov
Date 2014-04-14.17:25:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I think I have to add a work-around to Tulip anyway, because I don't want to have to tell people "you must upgrade your Python 3.3 otherwise this problem can happen" (if upgrading was easy for them they would be on 3.4 :-). So I don't care much if the 3.3 backport happens.
Date User Action Args
2014-04-14 17:25:35gvanrossumsetrecipients: + gvanrossum, ncoghlan, pitrou, vstinner, giampaolo.rodola, benjamin.peterson, python-dev, yselivanov, richard.kiss
2014-04-14 17:25:35gvanrossumsetmessageid: <>
2014-04-14 17:25:35gvanrossumlinkissue21209 messages
2014-04-14 17:25:35gvanrossumcreate