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 gregory.p.smith
Recipients alex, fil, francismb, gregory.p.smith, mark.dickinson, meador.inge, pitrou, skrah, tim.peters
Date 2013-12-10.01:43:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1386639806.21.0.173820513467.issue19904@psf.upfronthosting.co.za>
In-reply-to
Content
Pick two suitable letters for the int128 and uint128 cases and create a patch for an implementation with tests (targeting Python 3.5).  The implementation needs to compile and work even when the platform C compiler Python is compiled with does not have a 128-bit integer type (so the struct module always supports this rather than depending upon the platform native support in C).

I wouldn't bother with 256 and 512 bit integer support because I've never seen those used.  If that changes before 3.5 is released (a couple years), they can be added.
History
Date User Action Args
2013-12-10 01:43:26gregory.p.smithsetrecipients: + gregory.p.smith, tim.peters, mark.dickinson, pitrou, alex, skrah, meador.inge, francismb, fil
2013-12-10 01:43:26gregory.p.smithsetmessageid: <1386639806.21.0.173820513467.issue19904@psf.upfronthosting.co.za>
2013-12-10 01:43:26gregory.p.smithlinkissue19904 messages
2013-12-10 01:43:25gregory.p.smithcreate