Package: python-lockfile
Version: 1:0.8-2
Severity: important
The lockfile package does not correctly handle locking multiple files on Linux
systems. Consider the following script:
#!/usr/bin/env python
# -*- coding: iso-8859-1 -*-
import lockfile
import time
a = lockfile.FileLock('/tmp/a')
b = lockfile.FileLock('/tmp/b')
a.acquire()
b.acquire()
b.release()
a.release()
print 'Done!'
This script should clearly execute correctly (as long as /tmp is present) but
instead terminates with the following:
Traceback (most recent call last):
File "./test2.py", line 12, in <module>
a.release()
File "/usr/lib/pymodules/python2.6/lockfile.py", line 273, in release
raise NotMyLock
lockfile.NotMyLock
That is, it fails to release the *second* lock.
-- System Information:
Debian Release: 6.0.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python-lockfile depends on:
ii python 2.6.6-3+squeeze6 interactive high-level object-orie
ii python-support 1.0.10 automated rebuilding support for P
python-lockfile recommends no packages.
python-lockfile suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
