summaryrefslogtreecommitdiff
path: root/python-chkpkg.spec
blob: e052ca5807c8bd6be774b98aca1eb37cf8cd81e7 (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
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
%global _empty_manifest_terminate_build 0
Name:		python-chkpkg
Version:	0.5.2
Release:	1
Summary:	Tests Python package sources to see if they build successfully to a PyPi compatible distribution
License:	MIT
URL:		https://github.com/rtmigo/chkpkg_py#readme
Source0:	https://mirrors.aliyun.com/pypi/web/packages/55/e1/cb1967c83f65ee387c12dfcbb495804200fe20067c7ae2ab9821d6a48b3c/chkpkg-0.5.2.tar.gz
BuildArch:	noarch


%description
`chkpkg` supports Python 3.6+ on Linux, macOS and Windows.
# Install
``` bash
pip3 install chkpkg
```
# Use
``` python3
from chkpkg import Package
with Package() as pkg:
    pkg.run_python_code('import mypackage; mypackage.myfunc()')
    pkg.run_shell_code('mypackage_cli --version')
print("Package is OK!")
```
This **test script** creates a distribution from project sources, installs the
package from the distribution into a virtual environment, tries importing and
running the installed package from python and command line.
If any results in an error, an exception is thrown. The absence of exceptions
means that the package is fine.
By default, we assume that the `setup.py` or `setup.cfg` is located in the
current working directory. You can specify a different path using the
argument `Package(project_dir=...)`
# Steps
Without context, the test script would look like this:
``` python3
from chkpkg import Package
pkg = Package()
try:
    # step 1
    pkg.init()
    # step 2   
    pkg.run_python_code('import mypackage; mypackage.myfunc()')
    pkg.run_shell_code('mypackage_cli --version')
finally:
    # step 3
    pkg.cleanup()    
```
## Step 1: Build, Verify, Install
``` python3
pkg.init()
```
The `init` method:
- Creates a temporary virtual environment capable of building `.whl` files
    - Creates a distribution as a `.whl` file (`python -m build`)
    - Verifies the package source (`twine check --strict`)
- Creates another temporary virtual environment without preinstalled packages
    - Installs the package from the newly created `.whl` into the clean virtual
      environment
## Step 2: Import, Run
``` python3
pkg.run_python_code('import mypackage')
```
The `run_python_code` method allows you to check that the package is installed
and can be imported without errors.
You can also run some functions from the imported package and check the output.
``` python3
output = pkg.run_python_code('import mypackage; print(mypackage.plus(2, 3))')
assert output == "5"
```
If the package must be installed as a CLI program, this can be tested with
the `run_shell_code`. This function calls `cmd.exe` on Windows and `bash`
on other systems.
``` python3
output = pkg.run_shell_code('mypackage_cli --version')
assert output[0].isdigit()
```
The current working directory will be a random temporary one. If `mypackage_cli`
can be run, then it really is available as a shell command from any directory.
However, such tests are best done on a clean system. If we run the tests on
development machine, it may turn out that we are running a command that was in
the system before the package was installed.
## Step 3: Cleanup
``` python3
pkg.cleanup()
```
The `cleanup` method removes all temporary directories created during building
and testing.
# License
Copyright © 2021 [Arteom iG](https://github.com/rtmigo).
Released under the [MIT License](LICENSE).

%package -n python3-chkpkg
Summary:	Tests Python package sources to see if they build successfully to a PyPi compatible distribution
Provides:	python-chkpkg
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-chkpkg
`chkpkg` supports Python 3.6+ on Linux, macOS and Windows.
# Install
``` bash
pip3 install chkpkg
```
# Use
``` python3
from chkpkg import Package
with Package() as pkg:
    pkg.run_python_code('import mypackage; mypackage.myfunc()')
    pkg.run_shell_code('mypackage_cli --version')
print("Package is OK!")
```
This **test script** creates a distribution from project sources, installs the
package from the distribution into a virtual environment, tries importing and
running the installed package from python and command line.
If any results in an error, an exception is thrown. The absence of exceptions
means that the package is fine.
By default, we assume that the `setup.py` or `setup.cfg` is located in the
current working directory. You can specify a different path using the
argument `Package(project_dir=...)`
# Steps
Without context, the test script would look like this:
``` python3
from chkpkg import Package
pkg = Package()
try:
    # step 1
    pkg.init()
    # step 2   
    pkg.run_python_code('import mypackage; mypackage.myfunc()')
    pkg.run_shell_code('mypackage_cli --version')
finally:
    # step 3
    pkg.cleanup()    
```
## Step 1: Build, Verify, Install
``` python3
pkg.init()
```
The `init` method:
- Creates a temporary virtual environment capable of building `.whl` files
    - Creates a distribution as a `.whl` file (`python -m build`)
    - Verifies the package source (`twine check --strict`)
- Creates another temporary virtual environment without preinstalled packages
    - Installs the package from the newly created `.whl` into the clean virtual
      environment
## Step 2: Import, Run
``` python3
pkg.run_python_code('import mypackage')
```
The `run_python_code` method allows you to check that the package is installed
and can be imported without errors.
You can also run some functions from the imported package and check the output.
``` python3
output = pkg.run_python_code('import mypackage; print(mypackage.plus(2, 3))')
assert output == "5"
```
If the package must be installed as a CLI program, this can be tested with
the `run_shell_code`. This function calls `cmd.exe` on Windows and `bash`
on other systems.
``` python3
output = pkg.run_shell_code('mypackage_cli --version')
assert output[0].isdigit()
```
The current working directory will be a random temporary one. If `mypackage_cli`
can be run, then it really is available as a shell command from any directory.
However, such tests are best done on a clean system. If we run the tests on
development machine, it may turn out that we are running a command that was in
the system before the package was installed.
## Step 3: Cleanup
``` python3
pkg.cleanup()
```
The `cleanup` method removes all temporary directories created during building
and testing.
# License
Copyright © 2021 [Arteom iG](https://github.com/rtmigo).
Released under the [MIT License](LICENSE).

%package help
Summary:	Development documents and examples for chkpkg
Provides:	python3-chkpkg-doc
%description help
`chkpkg` supports Python 3.6+ on Linux, macOS and Windows.
# Install
``` bash
pip3 install chkpkg
```
# Use
``` python3
from chkpkg import Package
with Package() as pkg:
    pkg.run_python_code('import mypackage; mypackage.myfunc()')
    pkg.run_shell_code('mypackage_cli --version')
print("Package is OK!")
```
This **test script** creates a distribution from project sources, installs the
package from the distribution into a virtual environment, tries importing and
running the installed package from python and command line.
If any results in an error, an exception is thrown. The absence of exceptions
means that the package is fine.
By default, we assume that the `setup.py` or `setup.cfg` is located in the
current working directory. You can specify a different path using the
argument `Package(project_dir=...)`
# Steps
Without context, the test script would look like this:
``` python3
from chkpkg import Package
pkg = Package()
try:
    # step 1
    pkg.init()
    # step 2   
    pkg.run_python_code('import mypackage; mypackage.myfunc()')
    pkg.run_shell_code('mypackage_cli --version')
finally:
    # step 3
    pkg.cleanup()    
```
## Step 1: Build, Verify, Install
``` python3
pkg.init()
```
The `init` method:
- Creates a temporary virtual environment capable of building `.whl` files
    - Creates a distribution as a `.whl` file (`python -m build`)
    - Verifies the package source (`twine check --strict`)
- Creates another temporary virtual environment without preinstalled packages
    - Installs the package from the newly created `.whl` into the clean virtual
      environment
## Step 2: Import, Run
``` python3
pkg.run_python_code('import mypackage')
```
The `run_python_code` method allows you to check that the package is installed
and can be imported without errors.
You can also run some functions from the imported package and check the output.
``` python3
output = pkg.run_python_code('import mypackage; print(mypackage.plus(2, 3))')
assert output == "5"
```
If the package must be installed as a CLI program, this can be tested with
the `run_shell_code`. This function calls `cmd.exe` on Windows and `bash`
on other systems.
``` python3
output = pkg.run_shell_code('mypackage_cli --version')
assert output[0].isdigit()
```
The current working directory will be a random temporary one. If `mypackage_cli`
can be run, then it really is available as a shell command from any directory.
However, such tests are best done on a clean system. If we run the tests on
development machine, it may turn out that we are running a command that was in
the system before the package was installed.
## Step 3: Cleanup
``` python3
pkg.cleanup()
```
The `cleanup` method removes all temporary directories created during building
and testing.
# License
Copyright © 2021 [Arteom iG](https://github.com/rtmigo).
Released under the [MIT License](LICENSE).

%prep
%autosetup -n chkpkg-0.5.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-chkpkg -f filelist.lst
%dir %{python3_sitelib}/*

%files help -f doclist.lst
%{_docdir}/*

%changelog
* Tue Jun 20 2023 Python_Bot <Python_Bot@openeuler.org> - 0.5.2-1
- Package Spec generated