On Tue, Mar 18, 2008 at 1:13 PM, Marcin 'Qrczak' Kowalczyk <[EMAIL PROTECTED]> wrote: > Dnia 18-03-2008, Wt o godzinie 11:24 -0600, Adam Olsen pisze: > > > > If they need access to containing objects the only option is to use > > the underlying tool, deathqueues. > > Deathqueues are a part of python-safethread, right?
Yup > Interesting, but just like the finalization design, the design with > weakrefs being added to deathqueues instead of using weakref callbacks > is exactly what I consider the right design of weakrefs (or actually > it's a superset of my design which does not include a blocking wait). What sort of blocking wait do you use? Or did you mean you don't have one? > I see that you are implementing thread interrupts, which might be the > third thing that you are doing my way, and I am beginning to worry about > these coincidences. The interrupts seem to be unfinished in the patch > available to download, and the anonymous SVN is empty... The interrupt code is pretty rough and only implemented for a couple cases. If you look in test.test_sharedmodule, all the calls to sharedmodule.readloop() use it. All the interruption stuff will get renamed to "cancellation" at some point, as well as getting fleshed out a little more. -- Adam Olsen, aka Rhamphoryncus _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
