Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #19250 > unrolled thread

Re: __future__ and __rdiv__

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: __future__ and __rdiv__ Terry Reedy <tjreedy@udel.edu> - 2012-01-23 03:07 -0500
    Re: __future__ and __rdiv__ Duncan Booth <duncan.booth@invalid.invalid> - 2012-01-23 08:39 +0000

#19250 — Re: __future__ and __rdiv__

On 1/23/2012 12:22 AM, Massimo Di Pierro wrote:
> Hello everybody,
>
> I hope somebody could help me with this problem. If this is not the right place to ask, please direct me to the right place and apologies.
> I am using Python 2.7 and I am writing some code I want to work on 3.x as well. The problem can be reproduced with this code:
>
> # from __future__ import division
> class Number(object):
>      def __init__(self,number):
>          self.number=number
>      def __rdiv__(self,other):
>          return other/self.number
> print 10/Number(5)
>
> It prints 2 as I expect. But if I uncomment the first line, I get:

If you want to get 2 rather than 2.0 after uncommenting, then I believe 
you should use // and __floordiv__. In fact, you do not even need the 
future import. But if you mean for Number to be like a float rather than 
int, do as you are (with / and __truediv__).

Terry Jan Reedy

[toc] | [next] | [standalone]

#19253

Terry Reedy <tjreedy@udel.edu> wrote:

> But if you mean for Number to be like a float
> rather than int, do as you are (with / and __truediv__).
> 
Or even __rtruediv__


-- 
Duncan Booth http://kupuguy.blogspot.com

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web