[issue15894] _PyImport_ReInitLock() doesn't check return value of PyThread_acquire_lock

2012-11-15 Thread Brett Cannon
Brett Cannon added the comment: The chances of this being a problem is REALLY small and the single function that calls this is a public void function so there is no way for an exception to propagate short of a fatal error which seems a bit much. I did change to using NOWAIT_LOCK, though.

[issue15894] _PyImport_ReInitLock() doesn't check return value of PyThread_acquire_lock

2012-11-12 Thread Eric Snow
Changes by Eric Snow ericsnowcurren...@gmail.com: -- nosy: +eric.snow ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15894 ___ ___ Python-bugs-list

[issue15894] _PyImport_ReInitLock() doesn't check return value of PyThread_acquire_lock

2012-09-09 Thread Christian Heimes
New submission from Christian Heimes: Coverity claims that the call to PyThread_acquire_lock with NOWAIT_LOCK can fail. It sounds plausible as you don't wait for the lock to succeed. CID 486861: Unchecked return value (CHECKED_RETURN)At (3): Calling function

[issue15894] _PyImport_ReInitLock() doesn't check return value of PyThread_acquire_lock

2012-09-09 Thread Jesús Cea Avión
Changes by Jesús Cea Avión j...@jcea.es: -- nosy: +jcea ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15894 ___ ___ Python-bugs-list mailing list