%global _empty_manifest_terminate_build 0 Name: python-locket Version: 1.0.0 Release: 1 Summary: File-based locks for Python on Linux and Windows License: BSD-2-Clause URL: http://github.com/mwilliamson/locket.py Source0: https://mirrors.nju.edu.cn/pypi/web/packages/2f/83/97b29fe05cb6ae28d2dbd30b81e2e402a3eed5f460c26e9eaa5895ceacf5/locket-1.0.0.tar.gz BuildArch: noarch %description Locket implements a file-based lock that can be used by multiple processes provided they use the same path. import locket # Wait for lock with locket.lock_file("path/to/lock/file"): perform_action() # Raise LockError if lock cannot be acquired immediately with locket.lock_file("path/to/lock/file", timeout=0): perform_action() # Raise LockError if lock cannot be acquired after thirty seconds with locket.lock_file("path/to/lock/file", timeout=30): perform_action() # Without context managers: lock = locket.lock_file("path/to/lock/file") try: lock.acquire() perform_action() finally: lock.release() 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. * Calling ``release()`` on an unlocked lock raises ``LockError``. * Behaviour of locks after ``fork`` is undefined. %package -n python3-locket Summary: File-based locks for Python on Linux and Windows Provides: python-locket BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-locket Locket implements a file-based lock that can be used by multiple processes provided they use the same path. import locket # Wait for lock with locket.lock_file("path/to/lock/file"): perform_action() # Raise LockError if lock cannot be acquired immediately with locket.lock_file("path/to/lock/file", timeout=0): perform_action() # Raise LockError if lock cannot be acquired after thirty seconds with locket.lock_file("path/to/lock/file", timeout=30): perform_action() # Without context managers: lock = locket.lock_file("path/to/lock/file") try: lock.acquire() perform_action() finally: lock.release() 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. * Calling ``release()`` on an unlocked lock raises ``LockError``. * Behaviour of locks after ``fork`` is undefined. %package help Summary: Development documents and examples for locket Provides: python3-locket-doc %description help Locket implements a file-based lock that can be used by multiple processes provided they use the same path. import locket # Wait for lock with locket.lock_file("path/to/lock/file"): perform_action() # Raise LockError if lock cannot be acquired immediately with locket.lock_file("path/to/lock/file", timeout=0): perform_action() # Raise LockError if lock cannot be acquired after thirty seconds with locket.lock_file("path/to/lock/file", timeout=30): perform_action() # Without context managers: lock = locket.lock_file("path/to/lock/file") try: lock.acquire() perform_action() finally: lock.release() 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. * Calling ``release()`` on an unlocked lock raises ``LockError``. * Behaviour of locks after ``fork`` is undefined. %prep %autosetup -n locket-1.0.0 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-locket -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Thu Mar 09 2023 Python_Bot - 1.0.0-1 - Package Spec generated