automatic import of python-deprecation

3 files changed, 117 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..87406c8 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/deprecation-2.1.0.tar.gz
diff --git a/python-deprecation.spec b/python-deprecation.spec
new file mode 100644
index 0000000..93b2dac
--- /dev/null
+++ b/python-deprecation.spec
@@ -0,0 +1,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
+* Thu Mar 09 2023 Python_Bot <Python_Bot@openeuler.org> - 2.1.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..0833678
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+6b79c6572fb241e3cecbbd7d539bb66b  deprecation-2.1.0.tar.gz