In <[EMAIL PROTECTED]>, Paul McGuire wrote:
> <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>>
>>> PS Any news on when true division will be the default?
>>
>> Python 3.0 (aka P3K). It is the release that can break backwards
>> compatibility.
>>
>> http://www.python.org/dev/peps/p
<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
>> PS Any news on when true division will be the default?
>
> Python 3.0 (aka P3K). It is the release that can break backwards
> compatibility.
>
> http://www.python.org/dev/peps/pep-3000/
>
> casevh
>
Yes, Break Backwards Compatibilit
> PS Any news on when true division will be the default?
Python 3.0 (aka P3K). It is the release that can break backwards
compatibility.
http://www.python.org/dev/peps/pep-3000/
casevh
--
http://mail.python.org/mailman/listinfo/python-list
> Alan Isaac wrote:
> > Suppose x and y are ints in moduleA.
> >
> > If I put
> > from __future__ import division
> > in moduleA then x/y will produce the truediv result.
> >
> > If I put
> > from __future__ import division
> > in moduleB
> > and
> > from moduleB import *
> > in module A
> > then x
David Isaac wrote:
> Suppose x and y are ints in moduleA.
>
> If I put
> from __future__ import division
> in moduleA then x/y will produce the truediv result.
>
> If I put
> from __future__ import division
> in moduleB
> and
> from moduleB import *
> in module A
> then x/y will NOT produce the tru
Suppose x and y are ints in moduleA.
If I put
from __future__ import division
in moduleA then x/y will produce the truediv result.
If I put
from __future__ import division
in moduleB
and
from moduleB import *
in module A
then x/y will NOT produce the truediv result
(in moduleA).
Why?
And is ther
