On 5/28/06, Michael Hudson <[EMAIL PROTECTED]> wrote:
>
> I think I've fixed the refleaks too, but running regrtest -R :: takes
> rther a while.
FYI, I typically run -R 4:3: since it seems to do a pretty good job
and takes 20% less time. I never run -R with -u all, only a normal
run or specif
Michael Hudson wrote:
> Michael Hudson <[EMAIL PROTECTED]> writes:
>
>> I think I've fixed the refleaks too, but running regrtest -R :: takes
>> rther a while.
>
> I hadn't: test_codecs and test_codeccallbacks both leak, the latter
> quite spectacularly (9000+ refleaks a run). The test_codec
Michael Hudson <[EMAIL PROTECTED]> writes:
> I think I've fixed the refleaks too, but running regrtest -R :: takes
> rther a while.
I hadn't: test_codecs and test_codeccallbacks both leak, the latter
quite spectacularly (9000+ refleaks a run). The test_codecs leaks
come from calls to codecs.
Georg Brandl <[EMAIL PROTECTED]> writes:
> Michael Hudson wrote:
>> Georg Brandl <[EMAIL PROTECTED]> writes:
>>
>>> Michael Hudson wrote:
>>>
So I think I'll be reading through exceptions.c pretty carefully. I
don't think Sean and Richard have acquired as much paranoid
anal-minded
Michael Hudson wrote:
> Georg Brandl <[EMAIL PROTECTED]> writes:
>
>> Michael Hudson wrote:
>>
>>> So I think I'll be reading through exceptions.c pretty carefully. I
>>> don't think Sean and Richard have acquired as much paranoid
>>> anal-mindedness and I have when hacking on Python C internals
Georg Brandl <[EMAIL PROTECTED]> writes:
> Michael Hudson wrote:
>
>> So I think I'll be reading through exceptions.c pretty carefully. I
>> don't think Sean and Richard have acquired as much paranoid
>> anal-mindedness and I have when hacking on Python C internals yet :)
>
> I intended to go thr
Michael Hudson wrote:
> So I think I'll be reading through exceptions.c pretty carefully. I
> don't think Sean and Richard have acquired as much paranoid
> anal-mindedness and I have when hacking on Python C internals yet :)
I intended to go through the code again today or tomorrow, looking for
"Thomas Wouters" <[EMAIL PROTECTED]> writes:
> Does 'a tuple containing two Nones, a string and an int' ring a bell to
> anyone? :)
I found this one on the train (look at SyntaxError_init, it's
obvious). I also found a number of other bugs in the new exceptions.c
code, from leaks:
>>> def f():
On 5/28/06, Tim Peters <[EMAIL PROTECTED]> wrote:
[... a huge number of reference leaks reported ...]FYI, I "reduced" the relatively simple test_bisect's leaks to thisself-contained program:Funny, I reduced it to more or less the same thing, except the other way 'round: I suspected exceptions to be
[... a huge number of reference leaks reported ...]
FYI, I "reduced" the relatively simple test_bisect's leaks to this
self-contained program:
libreftest = """
No actual doctests here.
"""
import doctest
import gc
def main():
from sys import gettotalrefcount as trc
for i in range(10
10 matches
Mail list logo
