Antoine Pitrou pitrou.net> writes:
>
> Daniel Stutzbach stutzbachenterprises.com> writes:
> >
> > -1 on 1.+0 on 2.It'd be nice if we could postpone the resize if there are
> active iterators, but I don't think there's a clean way to track the
> iterators.
>
> I've started experimenting, and i
Daniel Stutzbach stutzbachenterprises.com> writes:
>
> -1 on 1.+0 on 2.It'd be nice if we could postpone the resize if there are
active iterators, but I don't think there's a clean way to track the iterators.
I've started experimenting, and it seems reasonably possible using a simple
guard class
Antoine Pitrou pitrou.net> writes:
>
> 1. Add the safe methods listkeys(), listitems(), listvalues() which would
> behave as the keys(), etc. methods from 2.x
>
> 2. Make it so that keys(), items(), values() atomically build a list of
> items internally, which makes them more costly for large
On Sun, Oct 11, 2009 at 10:50 AM, Antoine Pitrou wrote:
> In py3k, the weak dict methods keys(), values() and items() have been
> changed to return iterators (they returned lists in 2.x).
> However, it turns out that it makes these methods quite fragile, because
> a GC collection can occur wheneve
Hello,
In py3k, the weak dict methods keys(), values() and items() have been
changed to return iterators (they returned lists in 2.x).
However, it turns out that it makes these methods quite fragile, because
a GC collection can occur whenever during iterating, destroy one of the
weakref'ed obj
