This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients ajaksu2, dcjim, pitrou, vdupras
Date 2009-02-14.14:28:46
SpamBayes Score 1.8295223e-05
Marked as misclassified No
Message-id <1234621771.6357.2.camel@fsol>
In-reply-to <1234620688.95.0.248859697892.issue839159@psf.upfronthosting.co.za>
Content
> Results without the patch:
>  ./python.exe weakref_bench.py
> 0.804216861725
> 
> Results with the patch:
> $ ./python.exe weakref_bench.py
> 0.813000202179

Thanks for the numbers, I see my worries were unfounded.

> About the test_weak_*_dict_flushed_dead_items_when_iters_go_out:
> 
> If a weakref dict keeps its weak reference alive, it's not an 
> implementation detail, it's a bug. The whole point of using such dicts 
> is to not keep keys or values alive when they go out.

I was talking about doing `self.assertEqual(len(d), self.COUNT)` before
deleting the iterators.
History
Date User Action Args
2009-02-14 14:28:47pitrousetrecipients: + pitrou, dcjim, ajaksu2, vdupras
2009-02-14 14:28:46pitroulinkissue839159 messages
2009-02-14 14:28:46pitroucreate