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
|
%global _empty_manifest_terminate_build 0
Name: python-deprecation
Version: 2.1.0
Release: 1
Summary: A library to handle automated deprecations
License: Apache 2
URL: http://deprecation.readthedocs.io/
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/5a/d3/8ae2869247df154b64c1884d7346d412fed0c49df84db635aab2d1c40e62/deprecation-2.1.0.tar.gz
BuildArch: noarch
Requires: python3-packaging
%description
The ``deprecation`` library provides a ``deprecated`` decorator and a
``fail_if_not_removed`` decorator for your tests. Together, the two
enable the automation of several things:
1. The docstring of a deprecated method gets the deprecation details
appended to the end of it. If you generate your API docs direct
from your source, you don't need to worry about writing your own
notification. You also don't need to worry about forgetting to
write it. It's done for you.
2. Rather than having code live on forever because you only deprecated
it but never actually moved on from it, you can have your tests
tell you when it's time to remove the code. The ``@deprecated``
decorator can be told when it's time to entirely remove the code,
which causes ``@fail_if_not_removed`` to raise an ``AssertionError``,
causing either your unittest or py.test tests to fail.
See http://deprecation.readthedocs.io/ for the full documentation.
%package -n python3-deprecation
Summary: A library to handle automated deprecations
Provides: python-deprecation
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-deprecation
The ``deprecation`` library provides a ``deprecated`` decorator and a
``fail_if_not_removed`` decorator for your tests. Together, the two
enable the automation of several things:
1. The docstring of a deprecated method gets the deprecation details
appended to the end of it. If you generate your API docs direct
from your source, you don't need to worry about writing your own
notification. You also don't need to worry about forgetting to
write it. It's done for you.
2. Rather than having code live on forever because you only deprecated
it but never actually moved on from it, you can have your tests
tell you when it's time to remove the code. The ``@deprecated``
decorator can be told when it's time to entirely remove the code,
which causes ``@fail_if_not_removed`` to raise an ``AssertionError``,
causing either your unittest or py.test tests to fail.
See http://deprecation.readthedocs.io/ for the full documentation.
%package help
Summary: Development documents and examples for deprecation
Provides: python3-deprecation-doc
%description help
The ``deprecation`` library provides a ``deprecated`` decorator and a
``fail_if_not_removed`` decorator for your tests. Together, the two
enable the automation of several things:
1. The docstring of a deprecated method gets the deprecation details
appended to the end of it. If you generate your API docs direct
from your source, you don't need to worry about writing your own
notification. You also don't need to worry about forgetting to
write it. It's done for you.
2. Rather than having code live on forever because you only deprecated
it but never actually moved on from it, you can have your tests
tell you when it's time to remove the code. The ``@deprecated``
decorator can be told when it's time to entirely remove the code,
which causes ``@fail_if_not_removed`` to raise an ``AssertionError``,
causing either your unittest or py.test tests to fail.
See http://deprecation.readthedocs.io/ for the full documentation.
%prep
%autosetup -n deprecation-2.1.0
%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-deprecation -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Fri Apr 21 2023 Python_Bot <Python_Bot@openeuler.org> - 2.1.0-1
- Package Spec generated
|
