How to Install and Uninstall python2-locket Package on openSUSE Leap
Last updated: December 24,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "python2-locket" package
Please follow the steps below to install python2-locket on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
python2-locket
Copied
2. Uninstall "python2-locket" package
Please follow the instructions below to uninstall python2-locket on openSUSE Leap:
$
sudo zypper remove
python2-locket
Copied
3. Information about the python2-locket package on openSUSE Leap
Information for package python2-locket:
---------------------------------------
Repository : Main Repository
Name : python2-locket
Version : 0.2.0-bp153.1.15
Arch : noarch
Vendor : openSUSE
Installed Size : 16,4 KiB
Installed : No
Status : not installed
Source package : python-locket-0.2.0-bp153.1.15.src
Summary : File-based locks for Python
Description :
Locket implements a lock that can be used by multiple processes provided
they use the same path.
Locks largely behave as (non-reentrant) `Lock` instances from the `threading`
module in the standard library. Specifically, their behaviour is:
* Locks are uniquely identified by the file being locked,
both in the same process and across different processes.
* Locks are either in a locked or unlocked state.
* When the lock is unlocked, calling `acquire()` returns immediately and changes
the lock state to locked.
* When the lock is locked, calling `acquire()` will block until the lock state
changes to unlocked, or until the timeout expires.
* If a process holds a lock, any thread in that process can call `release()` to
change the state to unlocked.
* Behaviour of locks after `fork` is undefined.
---------------------------------------
Repository : Main Repository
Name : python2-locket
Version : 0.2.0-bp153.1.15
Arch : noarch
Vendor : openSUSE
Installed Size : 16,4 KiB
Installed : No
Status : not installed
Source package : python-locket-0.2.0-bp153.1.15.src
Summary : File-based locks for Python
Description :
Locket implements a lock that can be used by multiple processes provided
they use the same path.
Locks largely behave as (non-reentrant) `Lock` instances from the `threading`
module in the standard library. Specifically, their behaviour is:
* Locks are uniquely identified by the file being locked,
both in the same process and across different processes.
* Locks are either in a locked or unlocked state.
* When the lock is unlocked, calling `acquire()` returns immediately and changes
the lock state to locked.
* When the lock is locked, calling `acquire()` will block until the lock state
changes to unlocked, or until the timeout expires.
* If a process holds a lock, any thread in that process can call `release()` to
change the state to unlocked.
* Behaviour of locks after `fork` is undefined.