On 8/28/2013 11:15 AM, Neal Becker wrote:
The change in integer division seems to be the most insidious source of silent
errors in porting code from python2 - since it changes the behaviour or valid
code silently.
In Python since 2.??, put 'from __future__ import integer_division'
(sp?) at the
Chris Angelico wrote:
> On Thu, Aug 29, 2013 at 1:21 AM, Oscar Benjamin
> wrote:
>> On 28 August 2013 16:15, Neal Becker wrote:
>>> The change in integer division seems to be the most insidious source of
>>> silent errors in porting code from python2 - since it changes the behaviour
>>> or valid
On Thu, Aug 29, 2013 at 1:21 AM, Oscar Benjamin
wrote:
> On 28 August 2013 16:15, Neal Becker wrote:
>> The change in integer division seems to be the most insidious source of
>> silent
>> errors in porting code from python2 - since it changes the behaviour or valid
>> code silently.
>>
>> I wis
On Wed, Aug 28, 2013, at 11:15, Neal Becker wrote:
> The change in integer division seems to be the most insidious source of
> silent
> errors in porting code from python2 - since it changes the behaviour or
> valid
> code silently.
>
> I wish the interpreter had an instrumented mode to detect a
On 28 August 2013 16:15, Neal Becker wrote:
> The change in integer division seems to be the most insidious source of silent
> errors in porting code from python2 - since it changes the behaviour or valid
> code silently.
>
> I wish the interpreter had an instrumented mode to detect and report suc
The change in integer division seems to be the most insidious source of silent
errors in porting code from python2 - since it changes the behaviour or valid
code silently.
I wish the interpreter had an instrumented mode to detect and report such
problems.
--
http://mail.python.org/mailman/lis
