[issue9980] str(float) failure
report at bugs.python.org
Wed Sep 29 09:27:25 CEST 2010
Mark Dickinson <dickinsm at gmail.com> added the comment:
> I'm surprised that 3.2 fixes this: the float-to-string conversion code > is pretty much identical in both 3.1 and 3.2.
Whoops---not quite. The conversion code *is* pretty much identical, but 3.2 now uses a different algorithm for str (it's equal to repr now). So I'd expect that you'll see the issue in 3.2 too if you try something like
'%.12g' % 38210.0
Kiriakos, can you explain a bit more what the difference is between the 'remote engine' and the 'stand along interpreter'? Is the core Python library compiled using different compilers for these two?
Eric, are you able to reproduce this at all? I don't have access to Windows at the moment.
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list