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 mark.dickinson
Recipients collinwinter, eric.smith, gawain, gregory.p.smith, mark.dickinson, vstinner
Date 2009-09-09.21:11:04
SpamBayes Score 5.541795e-06
Marked as misclassified No
Message-id <1252530666.72.0.313065295051.issue6713@psf.upfronthosting.co.za>
In-reply-to
Content
On the other hand, _PyLong_Format currently contains general machinery 
for integer -> string conversion in any base in the range [2, 36], but I 
don't think that machinery is ever used for bases other than 2, 8, 10 
and 16.  So ripping _PyLong_Format out and just leaving the binary base 
and the suggested base 10 code might actually make longobject.c shorter.

I'd be interested to know how much the conversion of two digits at one 
time instead of one is contributing to the speedup by itself.  For large 
integers, I'd suspect that this makes very little difference.
History
Date User Action Args
2009-09-09 21:11:06mark.dickinsonsetrecipients: + mark.dickinson, collinwinter, gregory.p.smith, vstinner, eric.smith, gawain
2009-09-09 21:11:06mark.dickinsonsetmessageid: <1252530666.72.0.313065295051.issue6713@psf.upfronthosting.co.za>
2009-09-09 21:11:05mark.dickinsonlinkissue6713 messages
2009-09-09 21:11:04mark.dickinsoncreate