oslo_concurrency/lockutils.py | 5 4 + 1 - 0 !
1 file changed, 4 insertions(+), 1 deletion(-)

 [patch] use tempfile.tempdir for lock_path if oslo_lock_path is not
 set

DevStack spends a lot of time setting lock_path in a bunch of
locations.

http://codesearch.openstack.org/?q=oslo_concurrency%20lock_path&i=nope&files=&repos=

The default for lock_path is an environment variable
OSLO_LOCK_PATH.

http://codesearch.openstack.org/?q=OSLO_LOCK_PATH&i=nope&files=&repos=

Since the default is to consult an environment variable, which may not
even be set, this means that really there is no default. If you do
not set it - you end up getting errors like:

http://paste.openstack.org/show/488108/

Ideally - a library should have a reasonable default, where if a user
doesn't set something, the default will at least work. So, let's use
Python's built in tempfile module, which has fairly complex rules for
determining a sane directory to place temporary items in.

https://docs.python.org/2/library/tempfile.html#tempfile.tempdir

oslo_concurrency/tests/unit/test_processutils.py | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

 strip long integer suffix from strings. a proper fix would be
             more involved so I've opened a bug upstream.
Bug: https://bugs.launchpad.net/bugs/1552690