classification
Title: decimal.py: div_nearest ==> _div_nearest
Type: Stage: resolved
Components: Library (Lib) Versions: Python 2.5
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: ezio.melotti, mark.dickinson, skrah
Priority: normal Keywords: 26backport

Created on 2009-08-28 09:59 by skrah, last changed 2009-08-28 13:46 by mark.dickinson. This issue is now closed.

Messages (4)
msg92031 - (view) Author: Stefan Krah (skrah) * (Python committer) Date: 2009-08-28 09:59
--- a-decimal.py        2009-08-28 11:48:45.000000000 +0200
+++ b-decimal.py        2009-08-28 11:49:47.000000000 +0200
@@ -4845,7 +4845,7 @@
         log_tenpower = f*M # exact
     else:
         log_d = 0  # error < 2.31
-        log_tenpower = div_nearest(f, 10**-p) # error < 0.5
+        log_tenpower = _div_nearest(f, 10**-p) # error < 0.5
 
     return _div_nearest(log_tenpower+log_d, 100)
msg92033 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2009-08-28 10:23
This is already fixed in the trunk.
msg92037 - (view) Author: Stefan Krah (skrah) * (Python committer) Date: 2009-08-28 13:45
Yes, it is also fixed in 2.6 maintenance. I was hoping it could go into
2.5 maintenance.
msg92038 - (view) Author: Mark Dickinson (mark.dickinson) * (Python committer) Date: 2009-08-28 13:46
There's a security-fixes only policy in place for the 2.5 branch, so I'm 
afraid this isn't going to happen.
History
Date User Action Args
2009-08-28 13:46:16mark.dickinsonsetmessages: + msg92038
2009-08-28 13:45:12skrahsetmessages: + msg92037
2009-08-28 12:51:34r.david.murraysetkeywords: + 26backport
resolution: fixed -> out of date
2009-08-28 10:23:00ezio.melottisetstatus: open -> closed

nosy: + mark.dickinson, ezio.melotti
messages: + msg92033

resolution: fixed
stage: resolved
2009-08-28 09:59:53skrahcreate