automatic import of python-pycotap

3 files changed, 152 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..c87eae8 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/pycotap-1.2.2.tar.gz
diff --git a/python-pycotap.spec b/python-pycotap.spec
new file mode 100644
index 0000000..c2b588a
--- /dev/null
+++ b/python-pycotap.spec
@@ -0,0 +1,150 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-pycotap
+Version:	1.2.2
+Release:	1
+Summary:	A tiny test runner that outputs TAP results to standard output.
+License:	MIT
+URL:		https://el-tramo.be/pycotap
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/5c/c0/62b2c4749c380b20e9cd8a4729b32d2ac99fac0540c026a4c9347a1a546f/pycotap-1.2.2.tar.gz
+BuildArch:	noarch
+
+
+%description
+
+`pycotap` is a simple Python test runner for ``unittest`` that outputs 
+`Test Anything Protocol <http://testanything.org>`_ results directly to standard output.
+
+Contrary to other TAP runners for Python, ``pycotap`` ...
+
+- ... prints TAP (and *only* TAP) to standard output instead of to a separate file,
+  allowing you to pipe it directly to TAP pretty printers and processors 
+  (such as the ones listed on
+  `the tape page <https://www.npmjs.com/package/tape#pretty-reporters>`_). By
+  piping it to other consumers, you can avoid the need to add 
+  specific test runners to your test code. Since the TAP results
+  are printed as they come in, the consumers can directly display results while 
+  the tests are run.
+
+- ... only contains a TAP reporter, so no parsers, no frameworks, no dependencies, ...
+
+- ... is configurable: you can choose how you want the test output and test result
+  diagnostics to end up in your TAP output (as TAP diagnostics, YAML blocks, or 
+  attachments). The defaults are optimized for a `Jenkins <http://jenkins-ci.org>`_ based
+  flow.
+
+Documentation and examples can be found on `the pycotap page 
+<https://el-tramo.be/pycotap>`_.
+
+
+
+
+%package -n python3-pycotap
+Summary:	A tiny test runner that outputs TAP results to standard output.
+Provides:	python-pycotap
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-pycotap
+
+`pycotap` is a simple Python test runner for ``unittest`` that outputs 
+`Test Anything Protocol <http://testanything.org>`_ results directly to standard output.
+
+Contrary to other TAP runners for Python, ``pycotap`` ...
+
+- ... prints TAP (and *only* TAP) to standard output instead of to a separate file,
+  allowing you to pipe it directly to TAP pretty printers and processors 
+  (such as the ones listed on
+  `the tape page <https://www.npmjs.com/package/tape#pretty-reporters>`_). By
+  piping it to other consumers, you can avoid the need to add 
+  specific test runners to your test code. Since the TAP results
+  are printed as they come in, the consumers can directly display results while 
+  the tests are run.
+
+- ... only contains a TAP reporter, so no parsers, no frameworks, no dependencies, ...
+
+- ... is configurable: you can choose how you want the test output and test result
+  diagnostics to end up in your TAP output (as TAP diagnostics, YAML blocks, or 
+  attachments). The defaults are optimized for a `Jenkins <http://jenkins-ci.org>`_ based
+  flow.
+
+Documentation and examples can be found on `the pycotap page 
+<https://el-tramo.be/pycotap>`_.
+
+
+
+
+%package help
+Summary:	Development documents and examples for pycotap
+Provides:	python3-pycotap-doc
+%description help
+
+`pycotap` is a simple Python test runner for ``unittest`` that outputs 
+`Test Anything Protocol <http://testanything.org>`_ results directly to standard output.
+
+Contrary to other TAP runners for Python, ``pycotap`` ...
+
+- ... prints TAP (and *only* TAP) to standard output instead of to a separate file,
+  allowing you to pipe it directly to TAP pretty printers and processors 
+  (such as the ones listed on
+  `the tape page <https://www.npmjs.com/package/tape#pretty-reporters>`_). By
+  piping it to other consumers, you can avoid the need to add 
+  specific test runners to your test code. Since the TAP results
+  are printed as they come in, the consumers can directly display results while 
+  the tests are run.
+
+- ... only contains a TAP reporter, so no parsers, no frameworks, no dependencies, ...
+
+- ... is configurable: you can choose how you want the test output and test result
+  diagnostics to end up in your TAP output (as TAP diagnostics, YAML blocks, or 
+  attachments). The defaults are optimized for a `Jenkins <http://jenkins-ci.org>`_ based
+  flow.
+
+Documentation and examples can be found on `the pycotap page 
+<https://el-tramo.be/pycotap>`_.
+
+
+
+
+%prep
+%autosetup -n pycotap-1.2.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-pycotap -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Thu Mar 09 2023 Python_Bot <Python_Bot@openeuler.org> - 1.2.2-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..600834b
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+2904b19bbf76854a3e0673cd570b9dde  pycotap-1.2.2.tar.gz