automatic import of python-pyexpect

3 files changed, 89 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..8d66421 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/pyexpect-1.0.22.tar.gz
diff --git a/python-pyexpect.spec b/python-pyexpect.spec
new file mode 100644
index 0000000..05b1f9f
--- /dev/null
+++ b/python-pyexpect.spec
@@ -0,0 +1,87 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-pyexpect
+Version:	1.0.22
+Release:	1
+Summary:	Python expectaton library
+License:	ISC
+URL:		https://github.com/dwt/pyexpect
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/39/75/6e1cd39922639aece1c946da85cdcb85b91b3ac25f5aeece10ed20b0f065/pyexpect-1.0.22.tar.gz
+BuildArch:	noarch
+
+
+%description
+Line noise is reduced as much as possible, so the error message is displayed as near to the problematic code as possible. No stack traces to dig through, clear and consistent error messages that tell you what went wrong. Thats how assertions should work.
+## Why should I use expect() over self.assert*?
+Lets start with an example:
+    self.assertEquals('foo', 'bar')
+In this assertion it is not possible to see which of the arguments is the expected and which is the actual value. While this ordering is mostly internally consistent between the different assertions within the unittest package, it is certainly not consistent in how people use this package. This becomes even more unnerving if you switch unit test packages, teams and languages.
+The problem here is that the API has not way of knowing which of the two arguments is the expected value, and thus that information cannot be used in the error message.
+
+%package -n python3-pyexpect
+Summary:	Python expectaton library
+Provides:	python-pyexpect
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-pyexpect
+Line noise is reduced as much as possible, so the error message is displayed as near to the problematic code as possible. No stack traces to dig through, clear and consistent error messages that tell you what went wrong. Thats how assertions should work.
+## Why should I use expect() over self.assert*?
+Lets start with an example:
+    self.assertEquals('foo', 'bar')
+In this assertion it is not possible to see which of the arguments is the expected and which is the actual value. While this ordering is mostly internally consistent between the different assertions within the unittest package, it is certainly not consistent in how people use this package. This becomes even more unnerving if you switch unit test packages, teams and languages.
+The problem here is that the API has not way of knowing which of the two arguments is the expected value, and thus that information cannot be used in the error message.
+
+%package help
+Summary:	Development documents and examples for pyexpect
+Provides:	python3-pyexpect-doc
+%description help
+Line noise is reduced as much as possible, so the error message is displayed as near to the problematic code as possible. No stack traces to dig through, clear and consistent error messages that tell you what went wrong. Thats how assertions should work.
+## Why should I use expect() over self.assert*?
+Lets start with an example:
+    self.assertEquals('foo', 'bar')
+In this assertion it is not possible to see which of the arguments is the expected and which is the actual value. While this ordering is mostly internally consistent between the different assertions within the unittest package, it is certainly not consistent in how people use this package. This becomes even more unnerving if you switch unit test packages, teams and languages.
+The problem here is that the API has not way of knowing which of the two arguments is the expected value, and thus that information cannot be used in the error message.
+
+%prep
+%autosetup -n pyexpect-1.0.22
+
+%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-pyexpect -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Mon May 15 2023 Python_Bot <Python_Bot@openeuler.org> - 1.0.22-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..1a0b48f
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+4ef3874ba535b913d301e64aed0d78ac  pyexpect-1.0.22.tar.gz