blob: b5cfb13f381e4ada21d4c214a53d6625e897f695 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
|
%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::
<activate virtualenv for your project>
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::
<activate virtualenv for your 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::
<activate virtualenv for your project>
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::
<activate virtualenv for your 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::
<activate virtualenv for your project>
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::
<activate virtualenv for your 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 <Python_Bot@openeuler.org> - 2.4.4-1
- Package Spec generated
|
