diff options
Diffstat (limited to 'python-unittest2.spec')
| -rw-r--r-- | python-unittest2.spec | 120 |
1 files changed, 120 insertions, 0 deletions
diff --git a/python-unittest2.spec b/python-unittest2.spec new file mode 100644 index 0000000..fdb8b51 --- /dev/null +++ b/python-unittest2.spec @@ -0,0 +1,120 @@ +%global _empty_manifest_terminate_build 0 +Name: python-unittest2 +Version: 1.1.0 +Release: 1 +Summary: The new features in unittest backported to Python 2.4+. +License: UNKNOWN +URL: http://pypi.python.org/pypi/unittest2 +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/7f/c4/2b0e2d185d9d60772c10350d9853646832609d2f299a8300ab730f199db4/unittest2-1.1.0.tar.gz +BuildArch: noarch + + +%description +Differences between unittest2 and unittest in Python 2.7: +``assertItemsEqual`` does not silence Py3k warnings as this uses +``warnings.catch_warnings()`` which is new in Python 2.6 (and is used as a +context manager which would be a pain to make work with Python 2.4). +``TestCase.longMessage`` defaults to True because it is better. It defaults to +False in Python 2.7 for backwards compatibility reasons. +``python -m package`` doesn't work in versions of Python before Python 2.7. The +command line features of unittest2 are provided by a ``unit2`` (and +``unit2.py``) script instead. +unittest2 includes a very basic setuptools compatible test collector. Specify +``test_suite = 'unittest2.collector'`` in your setup.py. This starts test +discovery with the default parameters from the directory containing setup.py, so +it is perhaps most useful as an example (see unittest2/collector.py). +In unittest2 TextTestResult.stopTestRun is responsible for calling printErrors. +This is desirable behaviour but in Python 3.1 TestResult.stopTestRun was +documented as being empty and subclasses shouldn't need to call it. This would +make the change backwards incompatible and needs thinking about. + +%package -n python3-unittest2 +Summary: The new features in unittest backported to Python 2.4+. +Provides: python-unittest2 +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-unittest2 +Differences between unittest2 and unittest in Python 2.7: +``assertItemsEqual`` does not silence Py3k warnings as this uses +``warnings.catch_warnings()`` which is new in Python 2.6 (and is used as a +context manager which would be a pain to make work with Python 2.4). +``TestCase.longMessage`` defaults to True because it is better. It defaults to +False in Python 2.7 for backwards compatibility reasons. +``python -m package`` doesn't work in versions of Python before Python 2.7. The +command line features of unittest2 are provided by a ``unit2`` (and +``unit2.py``) script instead. +unittest2 includes a very basic setuptools compatible test collector. Specify +``test_suite = 'unittest2.collector'`` in your setup.py. This starts test +discovery with the default parameters from the directory containing setup.py, so +it is perhaps most useful as an example (see unittest2/collector.py). +In unittest2 TextTestResult.stopTestRun is responsible for calling printErrors. +This is desirable behaviour but in Python 3.1 TestResult.stopTestRun was +documented as being empty and subclasses shouldn't need to call it. This would +make the change backwards incompatible and needs thinking about. + +%package help +Summary: Development documents and examples for unittest2 +Provides: python3-unittest2-doc +%description help +Differences between unittest2 and unittest in Python 2.7: +``assertItemsEqual`` does not silence Py3k warnings as this uses +``warnings.catch_warnings()`` which is new in Python 2.6 (and is used as a +context manager which would be a pain to make work with Python 2.4). +``TestCase.longMessage`` defaults to True because it is better. It defaults to +False in Python 2.7 for backwards compatibility reasons. +``python -m package`` doesn't work in versions of Python before Python 2.7. The +command line features of unittest2 are provided by a ``unit2`` (and +``unit2.py``) script instead. +unittest2 includes a very basic setuptools compatible test collector. Specify +``test_suite = 'unittest2.collector'`` in your setup.py. This starts test +discovery with the default parameters from the directory containing setup.py, so +it is perhaps most useful as an example (see unittest2/collector.py). +In unittest2 TextTestResult.stopTestRun is responsible for calling printErrors. +This is desirable behaviour but in Python 3.1 TestResult.stopTestRun was +documented as being empty and subclasses shouldn't need to call it. This would +make the change backwards incompatible and needs thinking about. + +%prep +%autosetup -n unittest2-1.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-unittest2 -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Mon Apr 10 2023 Python_Bot <Python_Bot@openeuler.org> - 1.1.0-1 +- Package Spec generated |