Issue 13894: threading._CRLock should not be tested if _thread.RLock isn't implemented (original ) (raw ) Issue13894
Created on 2012-01-28 08:44 by anacrolix , last changed 2022-04-11 14:57 by admin . This issue is now closed .
Messages (3)
msg152151 - (view)
Author: Matt Joiner (anacrolix)
Date: 2012-01-28 08:44
_threading.RLock is optional, and threading._CRLock is set to None if it isn't available. If this happens, the test_threading unittests crash. Some implementations don't provide _thread.RLock. Patch attached.
msg152155 - (view)
Author: Roundup Robot (python-dev)
Date: 2012-01-28 10:38
New changeset 5cf181df7bea by Charles-François Natali in branch '3.2': Issue #13894 : Skip test_threading.CRLockTests if _CRLock isn't available. Patch http://hg.python.org/cpython/rev/5cf181df7bea New changeset 279b6d778663 by Charles-François Natali in branch 'default': Issue #13894 : Skip test_threading.CRLockTests if _CRLock isn't available. Patch http://hg.python.org/cpython/rev/279b6d778663
msg152157 - (view)
Author: Charles-François Natali (neologix) *
Date: 2012-01-28 10:39
Committed, thanks!
History
Date
User
Action
Args
2022-04-11 14:57:26
admin
set
github: 58102
2012-01-28 10:39:14
neologix
set
status: open -> closedcomponents: + Tests, - Library (Lib)versions: + Python 3.2nosy: + neologix messages: + resolution: fixedstage: resolved
2012-01-28 10:38:09
python-dev
set
nosy: + python-dev messages: +
2012-01-28 08:44:01
anacrolix
create