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 facundobatista, mark.dickinson, phd
Date 2008-03-25.18:41:53
SpamBayes Score 0.009588808
Marked as misclassified No
Message-id <1206470515.58.0.565024216976.issue2482@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not sure that converting to bytes for Python 3.0 is going to
be a simple change.  For one thing, most of the arithmetic functions
have to do the reverse conversion (int -> str/bytes) at some point.

At the moment, an int -> bytes conversion has to go through unicode (I 
think);  something like  bytes(str(n), 'ascii'), so it's not 100% clear
that replacing str with bytes is going to produce a speed gain.

For now, I'll get the fix for the 2.5/2.6 problem in (it only
involves changing 3 lines in decimal.py, along with adding a few
extra tests).

Changing str -> bytes in 3.0 needs more careful thought, and some 
benchmarking.
History
Date User Action Args
2008-03-25 18:41:56mark.dickinsonsetspambayes_score: 0.00958881 -> 0.009588808
recipients: + mark.dickinson, facundobatista, phd
2008-03-25 18:41:55mark.dickinsonsetspambayes_score: 0.00958881 -> 0.00958881
messageid: <1206470515.58.0.565024216976.issue2482@psf.upfronthosting.co.za>
2008-03-25 18:41:54mark.dickinsonlinkissue2482 messages
2008-03-25 18:41:54mark.dickinsoncreate