Hi all,
On Sun, Mar 26, 2006 at 11:39:50PM -0800, Neal Norwitz wrote:
> There are 5 tests that leak references that are present in 2.4.3c1,
> but not on HEAD. It would be great if someone can diagnose these and
> suggest a fix.
>
> test_doctest leaked [1, 1, 1] references
> test_pkg leaked [10,
Hi Michael,
On Sat, Apr 01, 2006 at 02:54:25PM +0100, Michael Hudson wrote:
> It's actually because somewhere in the bowels of compilation, the file
> name being compiled gets interned and test_pkg writes out some
> temporary files and imports them. If this doesn't happen on the
> trunk, did this
Armin Rigo <[EMAIL PROTECTED]> writes:
> Hi Neal,
>
> On Sun, Mar 26, 2006 at 11:39:50PM -0800, Neal Norwitz wrote:
>> test_pkg leaked [10, 10, 10] references
>
> This one at least appears to be caused by dummy (deleted) entries in the
> dictionary of interned strings. So it is not really a leak.
Neal Norwitz wrote:
> test_unicode leaked [7, 7, 7] references
And the last one came from
r41531 | neal.norwitz | 2005-11-24 23:09:18 +0100 (Do, 24 Nov 2005) | 1 line
Geänderte Pfade:
M /python/trunk/Python/codecs.c
M /python/trunk/Python/compile.c
M /python/trunk/Python/symtable.c
Fix
Neal Norwitz wrote:
> test_unicode leaked [7, 7, 7] references
This one is lacking this checkin:
r41530 | neal.norwitz | 2005-11-24 23:00:56 +0100 (Do, 24 Nov 2005) | 6
lines
Geänderte Pfade:
M /python/trunk/Lib/test/test_unicode.py
Move registration of the codec search function to the module
Hi Neal,
On Sun, Mar 26, 2006 at 11:39:50PM -0800, Neal Norwitz wrote:
> test_pkg leaked [10, 10, 10] references
This one at least appears to be caused by dummy (deleted) entries in the
dictionary of interned strings. So it is not really a leak. It is a
pain that it is so hard to figure this ou
There are 5 tests that leak references that are present in 2.4.3c1,
but not on HEAD. It would be great if someone can diagnose these and
suggest a fix.
test_doctest leaked [1, 1, 1] references
test_pkg leaked [10, 10, 10] references
test_pkgimport leaked [2, 2, 2] references
test_traceback leaked
