<br><div><span class="gmail_quote">On 5/28/06, <b class="gmail_sendername">Tim Peters</b> <<a href="mailto:tim.peters@gmail.com">tim.peters@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
[... a huge number of reference leaks reported ...]<br><br>FYI, I "reduced" the relatively simple test_bisect's leaks to this<br>self-contained program:</blockquote><div><br>Funny, I reduced it to more or less the same thing, except the other way 'round: I suspected exceptions to be the source of the leak, so I kept adding more complicated exception processing to my leak-test until it started leaking; it started leaking the moment I added a doctest to it, but not before. I somewhat doubt it's directly related to exceptions, though.
<br></div><br>Michael Hudson also mentioned it on #nfs, and it seems he went a little further:<br><br>00:54 <mwh> i found that test.test_support.check_syntax reliably leaks 5<br> references<br>00:55 <mwh> as does compile('1=1', '', 'exec') in fact
<br>00:58 <mwh> it's leaking a tuple containing two Nones a string and an int, i<br> think<br>01:00 <mwh> oh well, i guess sean and richard know what they changed...<br><br></div>Does 'a tuple containing two Nones, a string and an int' ring a bell to anyone? :)
<br clear="all"><br>-- <br>Thomas Wouters <<a href="mailto:thomas@python.org">thomas@python.org</a>><br><br>Hi! I'm a .signature virus! copy me into your .signature file to help me spread!