[issue1968] Unused number magic methods leaked into Py2.6

2008-01-31 Thread Jeffrey Yasskin
Jeffrey Yasskin added the comment: Done in r60480. -- resolution: accepted -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1968] Unused number magic methods leaked into Py2.6

2008-01-30 Thread Christian Heimes
Changes by Christian Heimes: -- priority: -> high type: -> behavior __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsub

[issue1968] Unused number magic methods leaked into Py2.6

2008-01-29 Thread Jeffrey Yasskin
Jeffrey Yasskin added the comment: Will do. -- components: +Library (Lib) resolution: -> accepted __ Tracker <[EMAIL PROTECTED]> __ ___ Python-

[issue1968] Unused number magic methods leaked into Py2.6

2008-01-29 Thread Raymond Hettinger
Raymond Hettinger added the comment: For 2.6, they should be omitted from rational.py. The code that is there is not the code that is run -- that impairs its value as a demo module. __ Tracker <[EMAIL PROTECTED]> _

[issue1968] Unused number magic methods leaked into Py2.6

2008-01-29 Thread Jeffrey Yasskin
Jeffrey Yasskin added the comment: I can't find the __round__, __ceil__, and __floor__ methods in int, long, and float. I left them in Rational on purpose, thinking that there might be a module that provided the new behaviors for 2.6 code, but you're probably right that these should be rolled bac

[issue1968] Unused number magic methods leaked into Py2.6

2008-01-29 Thread Raymond Hettinger
New submission from Raymond Hettinger: The Py2.6 code has __round__, __ceil__, and __floor__ methods still in several objects (int, longs, float, Rational) but they are not invoked by anything. For example, round(Rational(22,7)) does not use the Rational.__round__ code and round(22) does not us