2010/12/31
>
>>> Another example. I can totally remove the variable i, just using the
>>> stack, so a debugger (or, in general, having the tracing enabled)
> >> cannot even find something to change about it.
>
Ethan> -1
>
>Ethan> Debugging is challenging enough as it is -- wh
2010/12/31 Ethan Furman
> Cesare Di Mauro wrote:
>
> >
>
>> 2010/12/29 "Martin v. Löwis" wrote:
>>
> >>
>
>> Am 28.12.2010 18:08, schrieb Lukas Lueg:
>>>
Also, the load_fast in lne 22 to reference x could be taken out of the
>>> >>> loop as x will always point to the same object
>
>
ACTIVITY SUMMARY (2010-12-24 - 2010-12-31)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open2525 (-17)
closed 20058 (+49)
total 22583 (+32)
Open issues wit
>> Another example. I can totally remove the variable i, just using the
>> stack, so a debugger (or, in general, having the tracing enabled)
>> cannot even find something to change about it.
Ethan> -1
Ethan> Debugging is challenging enough as it is -- why would you want to
Cesare Di Mauro wrote:
>
2010/12/29 "Martin v. Löwis" wrote:
>>
Am 28.12.2010 18:08, schrieb Lukas Lueg:
Also, the load_fast in lne 22 to reference x could be taken out of the
>>> loop as x will always point to the same object
That's not true; a debugger may change the value of x.
An
2010/12/31 Maciej Fijalkowski
> On Fri, Dec 31, 2010 at 12:00 PM, Maciej Fijalkowski
> wrote:
> >> OK, but is it mandatory? For example, in the above code, I can unroll
> the
> >> loop because I found that range is the usual built-in, 5 is a low-enough
> >> constant,
> >
> > How do you know xran
On Fri, Dec 31, 2010 at 12:00 PM, Maciej Fijalkowski wrote:
>> OK, but is it mandatory? For example, in the above code, I can unroll the
>> loop because I found that range is the usual built-in, 5 is a low-enough
>> constant,
>
> How do you know xrange is xrange and not something else?
>
> Cheers,
> OK, but is it mandatory? For example, in the above code, I can unroll the
> loop because I found that range is the usual built-in, 5 is a low-enough
> constant,
How do you know xrange is xrange and not something else?
Cheers,
fijal
___
Python-Dev mail
