/usr/share/pyshared/zc.lockfile-1.0.2.egg-info/PKG-INFO is in python-zc.lockfile 1.0.2-0ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 | Metadata-Version: 1.1
Name: zc.lockfile
Version: 1.0.2
Summary: Basic inter-process locks
Home-page: http://www.python.org/pypi/zc.lockfile
Author: Jim Fulton
Author-email: jim@zope.com
License: ZPL 2.1
Description: *************************
Basic inter-process locks
*************************
The zc.lockfile package provides a basic portable implementation of
interprocess locks using lock files. The purpose if not specifically
to lock files, but to simply provide locks with an implementation
based on file-locking primitives. Of course, these locks could be
used to mediate access to *other* files. For example, the ZODB file
storage implementation uses file locks to mediate access to
file-storage database files. The database files and lock file files
are separate files.
.. contents::
Detailed Documentation
**********************
Lock file support
=================
The ZODB lock_file module provides support for creating file system
locks. These are locks that are implemented with lock files and
OS-provided locking facilities. To create a lock, instantiate a
LockFile object with a file name:
>>> import zc.lockfile
>>> lock = zc.lockfile.LockFile('lock')
If we try to lock the same name, we'll get a lock error:
>>> import zope.testing.loggingsupport
>>> handler = zope.testing.loggingsupport.InstalledHandler('zc.lockfile')
>>> try:
... zc.lockfile.LockFile('lock')
... except zc.lockfile.LockError:
... print "Can't lock file"
Can't lock file
>>> for record in handler.records: # doctest: +ELLIPSIS
... print record.levelname, record.getMessage()
ERROR Error locking file lock; pid=...
To release the lock, use it's close method:
>>> lock.close()
The lock file is not removed. It is left behind:
>>> import os
>>> os.path.exists('lock')
True
Of course, now that we've released the lock, we can create it again:
>>> lock = zc.lockfile.LockFile('lock')
>>> lock.close()
.. Cleanup
>>> import os
>>> os.remove('lock')
Change History
***************
1.0.2 (2012-12-02)
==================
- Fixed: the fix included in 1.0.1 caused multiple pids to be written
to the lock file
1.0.1 (2012-11-30)
==================
- Fixed: when there was lock contention, the pid in the lock file was
lost.
Thanks to Daniel Moisset reporting the problem and providing a fix
with tests.
- Added test extra to declare test dependency on ``zope.testing``.
- Using Python's ``doctest`` module instead of depreacted
``zope.testing.doctest``.
1.0.0 (2008-10-18)
==================
- Fixed a small bug in error logging.
1.0.0b1 (2007-07-18)
====================
Initial release
Download
**********************
Keywords: lock
Platform: UNKNOWN
Classifier: Programming Language :: Python
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: Zope Public License
Classifier: Operating System :: POSIX
Classifier: Operating System :: Microsoft :: Windows
|