%global _empty_manifest_terminate_build 0 Name: python-timer3 Version: 0.1.2 Release: 1 Summary: timer3 - Scheduler for Python functions. License: BSD URL: http://github.com/ask/timer/ Source0: https://mirrors.nju.edu.cn/pypi/web/packages/37/5a/05977765f1f0943a05865121e7fb79e93c98259245d89a5aa81fbab29039/timer3-0.1.2.tar.gz BuildArch: noarch %description The ``timer3`` module lets you schedule Python functions at specific times, or at an interval. It can be used as a replacement to ``threading.Timer``, the difference is that ``timer3`` is always only using a single thread (unless you manually start more of them) You should never use this to apply expensive operations, as this would not be effective when running in a single thread, rather you should make the timer move the operations to a execution pool (like a thread/multiprocessing pool, or maybe sending a message):: >>> pool = multiprocessing.Pool() >>> timer3.apply_after(10000, pool.apply_async, (expensive_fun, )) %package -n python3-timer3 Summary: timer3 - Scheduler for Python functions. Provides: python-timer3 BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-timer3 The ``timer3`` module lets you schedule Python functions at specific times, or at an interval. It can be used as a replacement to ``threading.Timer``, the difference is that ``timer3`` is always only using a single thread (unless you manually start more of them) You should never use this to apply expensive operations, as this would not be effective when running in a single thread, rather you should make the timer move the operations to a execution pool (like a thread/multiprocessing pool, or maybe sending a message):: >>> pool = multiprocessing.Pool() >>> timer3.apply_after(10000, pool.apply_async, (expensive_fun, )) %package help Summary: Development documents and examples for timer3 Provides: python3-timer3-doc %description help The ``timer3`` module lets you schedule Python functions at specific times, or at an interval. It can be used as a replacement to ``threading.Timer``, the difference is that ``timer3`` is always only using a single thread (unless you manually start more of them) You should never use this to apply expensive operations, as this would not be effective when running in a single thread, rather you should make the timer move the operations to a execution pool (like a thread/multiprocessing pool, or maybe sending a message):: >>> pool = multiprocessing.Pool() >>> timer3.apply_after(10000, pool.apply_async, (expensive_fun, )) %prep %autosetup -n timer3-0.1.2 %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-timer3 -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Mon May 15 2023 Python_Bot - 0.1.2-1 - Package Spec generated