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 pitrou
Recipients Jon.Oberheide, alex, christian.heimes, fijall, georg.brandl, hynek, loewis, ncoghlan, petri.lehtinen, pitrou, python-dev, serhiy.storchaka
Date 2012-06-21.12:14:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340280891.22.0.2821893881.issue15061@psf.upfronthosting.co.za>
In-reply-to
Content
> Shall explore option 2b) "optionally create a C implementation as it's much easier to check C code for timing issues"

Definitely. I'm not sure whether that can go in 3.3 post-beta, though.
History
Date User Action Args
2012-06-21 12:14:51pitrousetrecipients: + pitrou, loewis, georg.brandl, ncoghlan, christian.heimes, alex, fijall, python-dev, petri.lehtinen, hynek, serhiy.storchaka, Jon.Oberheide
2012-06-21 12:14:51pitrousetmessageid: <1340280891.22.0.2821893881.issue15061@psf.upfronthosting.co.za>
2012-06-21 12:14:50pitroulinkissue15061 messages
2012-06-21 12:14:50pitroucreate