Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Removed Exact/Inexact after discussion with Yasskin. | Raymond Hettinger | 2008-03-15 | 1 | -9/+0 |
| | | | | | | | | | | | | | | | Unlike Scheme where exactness is implemented as taints, the Python implementation associated exactness with data types. This created inheritance issues (making an exact subclass of floats would result in the subclass having both an explicit Exact registration and an inherited Inexact registration). This was a problem for the decimal module which was designed to span both exact and inexact arithmetic. There was also a question of use cases and no examples were found where ABCs for exactness could be used to improve code. One other issue was having separate tags for both the affirmative and negative cases. This is at odds with the approach taken elsewhere in the Python (i.e. we don't have an ABC both Hashable and Unhashable). | ||||
* | Move __builtins__.trunc() to math.trunc() per | Jeffrey Yasskin | 2008-02-01 | 1 | -6/+7 |
| | | | | | http://mail.python.org/pipermail/python-dev/2008-January/076626.html and issue 1965. | ||||
* | Backport PEP 3141 from the py3k branch to the trunk. This includes r50877 (just | Jeffrey Yasskin | 2008-01-03 | 1 | -0/+62 |
the complex_pow part), r56649, r56652, r56715, r57296, r57302, r57359, r57361, r57372, r57738, r57739, r58017, r58039, r58040, and r59390, and new documentation. The only significant difference is that round(x) returns a float to preserve backward-compatibility. See http://bugs.python.org/issue1689. |