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 noam
Recipients christian.heimes, gvanrossum, nascheme, noam, rhettinger, tim.peters
Date 2007-12-18.08:09:24
SpamBayes Score 0.0005073622
Marked as misclassified No
Message-id <b348a0850712180009m105d7839re7a5485664ad4829@mail.gmail.com>
In-reply-to <1197962934.82.0.580628845621.issue1580@psf.upfronthosting.co.za>
Content
I think that we can give up float(repr(x)) == x across different
platforms, since we don't guarantee something more basic: We don't
guarantee that the same program doing only floating point operations
will produce the same results across different 754 platforms, because
in the compilation process we rely on the system's decimal to binary
conversion. In other words, using the current repr(), one can pass a
value x from platform A platform B and be sure to get the same value.
But if he has a python function f, he can't be sure that f(x) on
platform A will result in the same value as f(x) on platform B. So the
cross-platform repr() doesn't really matter.

I like eval(repr(x)) == x because it means that repr(x) captures all
the information about x, not because it lets me pass x from one
platform to another. For communication, I use other methods.
History
Date User Action Args
2007-12-18 08:09:25noamsetspambayes_score: 0.000507362 -> 0.0005073622
recipients: + noam, gvanrossum, tim.peters, nascheme, rhettinger, christian.heimes
2007-12-18 08:09:24noamlinkissue1580 messages
2007-12-18 08:09:24noamcreate