%global _empty_manifest_terminate_build 0 Name: python-ubiquerg Version: 0.6.2 Release: 1 Summary: Various utility functions License: BSD-2-Clause URL: https://github.com/pepkit/ubiquerg/ Source0: https://mirrors.nju.edu.cn/pypi/web/packages/b3/25/a9bc26700e5f4d8f4b174ccf20c4780960713adf56ce4023d6b814833b70/ubiquerg-0.6.2.tar.gz BuildArch: noarch %description # ubiquerg ![Run pytests](https://github.com/pepkit/ubiquerg/workflows/Run%20pytests/badge.svg) [![codecov](https://codecov.io/gh/pepkit/ubiquerg/branch/master/graph/badge.svg)](https://codecov.io/gh/pepkit/ubiquerg) [![PEP compatible](https://pepkit.github.io/img/PEP-compatible-green.svg)](https://pepkit.github.io) Ubiquerg is a utility package with a collection of helpful universally useful functions. The name means work (erg) everywhere (ubique), indicating our intention for these to be low-level functions that can be used in lots of different places. Functions are divided into groups, including: - collection - environment - files - paths - system - web - cli_tools ## Development guidelines - Ubiquerg should have no dependencies outside of standard built-in python modules. Please do not add any functions that introduce a new dependency. - Functions should be generic. They should perform basic, low-level processing that is not specific to a particular application. - Functions should only be added to ubiquerg if they are used in at least 2 existing modules. - Functions should be kept relatively small and simple (ideally <50 lines of code). %package -n python3-ubiquerg Summary: Various utility functions Provides: python-ubiquerg BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-ubiquerg # ubiquerg ![Run pytests](https://github.com/pepkit/ubiquerg/workflows/Run%20pytests/badge.svg) [![codecov](https://codecov.io/gh/pepkit/ubiquerg/branch/master/graph/badge.svg)](https://codecov.io/gh/pepkit/ubiquerg) [![PEP compatible](https://pepkit.github.io/img/PEP-compatible-green.svg)](https://pepkit.github.io) Ubiquerg is a utility package with a collection of helpful universally useful functions. The name means work (erg) everywhere (ubique), indicating our intention for these to be low-level functions that can be used in lots of different places. Functions are divided into groups, including: - collection - environment - files - paths - system - web - cli_tools ## Development guidelines - Ubiquerg should have no dependencies outside of standard built-in python modules. Please do not add any functions that introduce a new dependency. - Functions should be generic. They should perform basic, low-level processing that is not specific to a particular application. - Functions should only be added to ubiquerg if they are used in at least 2 existing modules. - Functions should be kept relatively small and simple (ideally <50 lines of code). %package help Summary: Development documents and examples for ubiquerg Provides: python3-ubiquerg-doc %description help # ubiquerg ![Run pytests](https://github.com/pepkit/ubiquerg/workflows/Run%20pytests/badge.svg) [![codecov](https://codecov.io/gh/pepkit/ubiquerg/branch/master/graph/badge.svg)](https://codecov.io/gh/pepkit/ubiquerg) [![PEP compatible](https://pepkit.github.io/img/PEP-compatible-green.svg)](https://pepkit.github.io) Ubiquerg is a utility package with a collection of helpful universally useful functions. The name means work (erg) everywhere (ubique), indicating our intention for these to be low-level functions that can be used in lots of different places. Functions are divided into groups, including: - collection - environment - files - paths - system - web - cli_tools ## Development guidelines - Ubiquerg should have no dependencies outside of standard built-in python modules. Please do not add any functions that introduce a new dependency. - Functions should be generic. They should perform basic, low-level processing that is not specific to a particular application. - Functions should only be added to ubiquerg if they are used in at least 2 existing modules. - Functions should be kept relatively small and simple (ideally <50 lines of code). %prep %autosetup -n ubiquerg-0.6.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-ubiquerg -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Wed Apr 12 2023 Python_Bot - 0.6.2-1 - Package Spec generated