A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2000-November/010392.html below:

[Python-Dev] Re: Revamping Python's Numeric Model

[Python-Dev] Re: Revamping Python's Numeric Model [Python-Dev] Re: Revamping Python's Numeric ModelMoshe Zadka moshez@zadka.site.co.il
Sun, 05 Nov 2000 10:20:45 +0200
[Martin v. Loewis]
> It's not inherently wrong. It just points out an omission in the PEP:
> it doesn't talk about the meaning of number literals.

That's right -- but I did mean that floating-point literals will be
inexact.

> Since the new
> model is going to follow algebraic principles more closely, I had
> expected that
> 
>   0.333333333 == 333333333 / 1000000000
> 
> where, as I understand the proposal, the right-hand side is an exact
> number (so 0.333333333*3 would be 999999999 / 1000000000).
> 
> One of the more-frequent questions on python-help is confusion about
> floating-point numbers, e.g. why is the result of 1.99+4.99 printed
> as 6.9800000000000004; users often report that as a bug.

That's one thing my PEP is not meant to help with -- floating point
numbers will remain hard. Hopefully, people will use them less often
when they'll have rational arithmetic.

-- 
Moshe Zadka <sig@zadka.site.co.il>



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4