delta/cpython-git.git/Lib/threading.py, branch v2.2.3c1 github.com: python/cpython.git backport: 2003-02-02T19:24:38+00:00 Neal Norwitz nnorwitz@gmail.com 2003-02-02T19:24:38+00:00 a9adbff3df8384d73282d558ae5e52591a874820 revision 1.29 date: 2002/11/21 21:08:39; author: gvanrossum; state: Exp; lines: +14 -8 The _Event class should be more careful with releasing its lock when interrupted. A try/finally will do nicely. Maybe other classes need this too, but since they manipulate more state it's less clear that that is always the right thing, and I'm in a hurry. 
revision 1.29
date: 2002/11/21 21:08:39;  author: gvanrossum;  state: Exp;  lines: +14 -8
The _Event class should be more careful with releasing its lock when
interrupted.  A try/finally will do nicely.  Maybe other classes need
this too, but since they manipulate more state it's less clear that
that is always the right thing, and I'm in a hurry.
SF #515023. Make _DummyThread.join() signature match base class (Thread) 2002-02-19T03:02:33+00:00 Neal Norwitz nnorwitz@gmail.com 2002-02-19T03:02:33+00:00 0970905f99a9a14563dc6b1a7b5d9f4936af2f08 






Backport gvanrossum's checkin of revision 1.20:
2002-01-04T12:29:45+00:00

Michael W. Hudson
mwh@python.net

2002-01-04T12:29:45+00:00

c8ae21a8647a01049f0ee8b178bbb8bb4856c35f

Thread.__bootstrap(): ignore exceptions in the self.__delete() call in
the finally clause.  An exception here could happen when a daemon
thread exits after the threading module has already been trashed by
the import finalization, and there's not much of a point in trying to
insist doing the cleanup in that stage.

This should fix SF bug ##497111: active_limbo_lock error at program
exit.

2.1.2 and 2.2.1 Bugfix candidate!

(has this gone into 2.1.2 yet?)





Thread.__bootstrap(): ignore exceptions in the self.__delete() call in
the finally clause.  An exception here could happen when a daemon
thread exits after the threading module has already been trashed by
the import finalization, and there's not much of a point in trying to
insist doing the cleanup in that stage.

This should fix SF bug ##497111: active_limbo_lock error at program
exit.

2.1.2 and 2.2.1 Bugfix candidate!

(has this gone into 2.1.2 yet?)







Whitespace normalization.
2001-09-18T02:26:39+00:00

Tim Peters
tim.peters@gmail.com

2001-09-18T02:26:39+00:00

b64bec3ec078d66a34175b9dec55eaac5c821b46












Patch #428326: New class threading.Timer.
2001-09-05T13:44:54+00:00

Martin v. Löwis
martin@v.loewis.de

2001-09-05T13:44:54+00:00

44f8696171f8d9e29c82e250ed90351dfb207da2












Added new BoundedSemaphore class.  Closes bug 452836.
2001-08-20T20:27:58+00:00

Skip Montanaro
skip@pobox.com

2001-08-20T20:27:58+00:00

e428bb703010317dc6f87c9a1e709dff8e078535












of course I muffed it separating the notes code from the initial_value
2001-08-19T05:53:47+00:00

Skip Montanaro
skip@pobox.com

2001-08-19T05:53:47+00:00

ae8454aeb3d49d464b762690d014cf11da3370c0

code.  grrr...





code.  grrr...







add debug calls to self._note for the Semaphore class.  This closes bug
2001-08-19T04:25:24+00:00

Skip Montanaro
skip@pobox.com

2001-08-19T04:25:24+00:00

b446fc7f2749c2335fc301d60e8f011d447875d3

443614.  I will submit a new feature request and patch to threading.py and
libthreading.tex to address the bounded semaphore issue.





443614.  I will submit a new feature request and patch to threading.py and
libthreading.tex to address the bounded semaphore issue.







Remove unused imports (PyChecker)
2001-08-13T14:40:29+00:00

Andrew M. Kuchling
amk@amk.ca

2001-08-13T14:40:29+00:00

a49e0a0893ed83f0571b19fc29a3263edf53e7f6












_Condition.wait():  never sleep longer than the timeout time remaining,
2001-08-12T00:41:33+00:00

Tim Peters
tim.peters@gmail.com

2001-08-12T00:41:33+00:00

a6a4f27ef7c80e6dee626d6649f2019544b24f65

and even if we have a long time left to wait, try the lock at least 20
times/second.





and even if we have a long time left to wait, try the lock at least 20
times/second.