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 gvanrossum
Recipients christian.heimes, gvanrossum, nascheme, noam, tim.peters
Date 2007-12-11.15:21:18
SpamBayes Score 0.0009774554
Marked as misclassified No
Message-id <>
(1) Despite Tim's grave language, I don't think we'll need to write our
own correctly-rounding float input routine.  We can just say that Python
won't work correctly unless your float input routine is rounding
correctly; a unittest should detect whether this is the case.  I expect
that more recent C runtimes for Windows are correct.

(1a) Perhaps it's better to only do this for Python 3.0, which has a
smaller set of platforms to support.

(2) Have you two (Christian and Noam) figured out yet why repr(1e5) is
'1.0' on some platforms?  If it's not byte order (and I no longer
believe it is) what could it be?  An uninitialized variable?  It doesn't
seem to vary with the processor, but it could vary with the C runtime or OS.

(3) Detecting NaNs and infs in a platform-independent way is tricky,
probably beyond you (I know it's beyond me).  (Of course, producing
standardized output for them and recognizing these as input is easy, and
that should definitely be done.)

(4) Looks like we've been a bit too hasty checking this in.  Let's be
extra careful for round #2.
Date User Action Args
2007-12-11 15:21:20gvanrossumsetspambayes_score: 0.000977455 -> 0.0009774554
recipients: + gvanrossum, tim.peters, nascheme, christian.heimes, noam
2007-12-11 15:21:20gvanrossumsetspambayes_score: 0.000977455 -> 0.000977455
messageid: <>
2007-12-11 15:21:20gvanrossumlinkissue1580 messages
2007-12-11 15:21:18gvanrossumcreate