David Watson <bai...@users.sourceforge.net> added the comment: > Is this still an issue on later versions of Python and/or FreeBSD?
Yes, there is still an issue. There is no longer a deadlock on FreeBSD because the module been changed to use only lockf() and dot-locking (on all platforms), but the issue is now about how users can enable other locking mechanisms that they need, such as flock(), without causing a deadlock on platforms where they refer to the same lock as lockf(). They can't just override the classes' .lock() and .unlock() methods, because some parts of the code perform locking operations directly without calling those methods. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1512163> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
