%global _empty_manifest_terminate_build 0 Name: python-pip-check-reqs Version: 2.4.4 Release: 1 Summary: Find packages that should or should not be in requirements for a project License: MIT URL: https://github.com/r1chardj0n3s/pip-check-reqs Source0: https://mirrors.nju.edu.cn/pypi/web/packages/77/89/a8dffbc53ac922859144409dd3901cdf586d51ba908a620b47fa266e9bad/pip_check_reqs-2.4.4.tar.gz BuildArch: noarch Requires: python3-packaging Requires: python3-pip Requires: python3-black Requires: python3-flake8 Requires: python3-isort Requires: python3-mypy Requires: python3-pyenchant Requires: python3-pylint Requires: python3-pytest Requires: python3-pytest-cov Requires: python3-types-setuptools %description It happens: you start using a module in your project and it works and you don't realise that it's only being included in your `virtualenv`_ because it's a dependency of a package you're using. pip-missing-reqs finds those modules so you can include them in the `requirements.txt`_ for the project. Alternatively, you have a long-running project that has some packages in requirements.txt that are no longer actively used in the codebase. The pip-extra-reqs tool will find those modules so you can remove them. Assuming your project follows a layout like the suggested sample project:: setup.py setup.cfg requirements.txt sample/__init__.py sample/sample.py sample/tests/test_sample.py Basic usage, running in your project directory:: pip-missing-reqs --ignore-file=sample/tests/* sample This will find all imports in the code in "sample" and check that the packages those modules belong to are in the requirements.txt file. Additionally it is possible to check that there are no dependencies in requirements.txt that are then unused in the project:: pip-extra-reqs --ignore-file=sample/tests/* sample This would find anything that is listed in requirements.txt but that is not imported by sample. %package -n python3-pip-check-reqs Summary: Find packages that should or should not be in requirements for a project Provides: python-pip-check-reqs BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-pip-check-reqs It happens: you start using a module in your project and it works and you don't realise that it's only being included in your `virtualenv`_ because it's a dependency of a package you're using. pip-missing-reqs finds those modules so you can include them in the `requirements.txt`_ for the project. Alternatively, you have a long-running project that has some packages in requirements.txt that are no longer actively used in the codebase. The pip-extra-reqs tool will find those modules so you can remove them. Assuming your project follows a layout like the suggested sample project:: setup.py setup.cfg requirements.txt sample/__init__.py sample/sample.py sample/tests/test_sample.py Basic usage, running in your project directory:: pip-missing-reqs --ignore-file=sample/tests/* sample This will find all imports in the code in "sample" and check that the packages those modules belong to are in the requirements.txt file. Additionally it is possible to check that there are no dependencies in requirements.txt that are then unused in the project:: pip-extra-reqs --ignore-file=sample/tests/* sample This would find anything that is listed in requirements.txt but that is not imported by sample. %package help Summary: Development documents and examples for pip-check-reqs Provides: python3-pip-check-reqs-doc %description help It happens: you start using a module in your project and it works and you don't realise that it's only being included in your `virtualenv`_ because it's a dependency of a package you're using. pip-missing-reqs finds those modules so you can include them in the `requirements.txt`_ for the project. Alternatively, you have a long-running project that has some packages in requirements.txt that are no longer actively used in the codebase. The pip-extra-reqs tool will find those modules so you can remove them. Assuming your project follows a layout like the suggested sample project:: setup.py setup.cfg requirements.txt sample/__init__.py sample/sample.py sample/tests/test_sample.py Basic usage, running in your project directory:: pip-missing-reqs --ignore-file=sample/tests/* sample This will find all imports in the code in "sample" and check that the packages those modules belong to are in the requirements.txt file. Additionally it is possible to check that there are no dependencies in requirements.txt that are then unused in the project:: pip-extra-reqs --ignore-file=sample/tests/* sample This would find anything that is listed in requirements.txt but that is not imported by sample. %prep %autosetup -n pip-check-reqs-2.4.4 %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-pip-check-reqs -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Tue Apr 25 2023 Python_Bot - 2.4.4-1 - Package Spec generated