Joshua Harlow 2f4bd6897d Use a thread-identifier that can't easily be recycled ...

Since it is possible for a thread-id from get_ident() to
potentially be recycled at some point in the future it is
safer to use a object that will only be recycled when there
are no more references to it (including the references held
in the reader-writer lock internals).

This avoids any type of thread-identifier recycling issues
that could be possible since it is now assured that said
recycling will not happen until the reader-writer lock itself
is cleaned up by the garbage collector.

Change-Id: I2ea693fe8fc129943648edef8ed6c3596772ebc0

2015-02-04 22:30:59 -08:00

..

__init__.py

Removed copyright from empty files

2014-02-22 17:16:29 +08:00

async_utils.py

Use importutils.try_import for optional eventlet imports

2015-01-25 11:10:14 -08:00

deprecation.py

Switch to using 'oslo_utils' vs 'oslo.utils'

2015-01-14 23:56:11 -08:00

eventlet_utils.py

Use importutils.try_import for optional eventlet imports

2015-01-25 11:10:14 -08:00

kazoo_utils.py

Make all/most usage of type errors follow a similar pattern

2015-01-23 18:25:01 -08:00

kombu_utils.py

Add and use a nicer kombu message formatter

2015-01-29 22:59:54 -08:00

lock_utils.py

Use a thread-identifier that can't easily be recycled

2015-02-04 22:30:59 -08:00

misc.py

Use monotonic time when/if available

2015-01-27 10:14:40 -08:00

persistence_utils.py

Switch to using 'oslo_utils' vs 'oslo.utils'

2015-01-14 23:56:11 -08:00

threading_utils.py

Add a thread bundle helper utility + tests

2015-01-24 18:33:51 -08:00