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 amaury.forgeotdarc, georg.brandl, ggenellina, gregory.p.smith, gvanrossum, pitrou, rhettinger, spiv
Date 2008-01-22.00:05:33
SpamBayes Score 0.40407598
Marked as misclassified No
Message-id <1200960335.08.0.080846315856.issue1703448@psf.upfronthosting.co.za>
In-reply-to
Content
__delete() already acquires _active_limbo_lock so your proposal must be
changed for the following:

            with _active_limbo_lock:
                self.__stop()
                try:
                    del _active[_get_ident()]
                except:
                    pass

However, with this slight correction it seems to work. I was worrying
whether another thread could hold __block (which is acquired in
__stop()) while waiting for _active_limbo_lock to be released, but
AFAICT there doesn't seem to be a code path where it can happen...
History
Date User Action Args
2008-01-22 00:05:35pitrousetspambayes_score: 0.404076 -> 0.40407598
recipients: + pitrou, gvanrossum, georg.brandl, rhettinger, gregory.p.smith, spiv, amaury.forgeotdarc, ggenellina
2008-01-22 00:05:35pitrousetspambayes_score: 0.404076 -> 0.404076
messageid: <1200960335.08.0.080846315856.issue1703448@psf.upfronthosting.co.za>
2008-01-22 00:05:33pitroulinkissue1703448 messages
2008-01-22 00:05:33pitroucreate