- Update to version 3.5.3:

+ Line numbers in the HTML report line up better with the source lines, fixing
    issue 197
  + When specifying a directory as the source= option, the directory itself no
    longer needs to have a __init__.py file, though its subdirectories do, to
    be considered as source files.
  + Files encoded as UTF-8 with a BOM are now properly handled, fixing
    issue 179_.
  + Fixed more cases of non-Python files being reported as Python source, and
    then not being able to parse them as Python.  Closes issue 82 (again).
  + Fixed memory leaks under Python 3, thanks, Brett Cannon. Closes issue 147_.
  + Optimized .pyo files may not have been handled correctly, issue 195_.
  + Certain unusually named file paths could have been mangled during reporting,
    issue 194_.
  + Try to do a better job of the impossible task of detecting when we can't
    build the C extension, fixing issue 183_.
  + Testing is now done with tox
- Changes from version 3.5.2:
  + No changes since 3.5.2.b1
- Changes from version 3.5.2b1
  + The HTML report has slightly tweaked controls: the buttons at the top of
    the page are color-coded to the source lines they affect.
  + Custom CSS can be applied to the HTML report by specifying a CSS file as
    the extra_css configuration value in the [html] section.
  + Source files with custom encodings declared in a comment at the top are now
    properly handled during reporting on Python 2.  Python 3 always handled them
    properly.  This fixes issue 157_.
  + Backup files left behind by editors are no longer collected by the source=
    option, fixing issue 168_.
  + If a file doesn't parse properly as Python, we don't report it as an error

OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-coverage?expand=0&rev=20

python3-coverage.spec

@@ -17,7 +17,7 @@
 
 
 Name:           python3-coverage
-Version:        3.5.1
+Version:        3.5.3
 Release:        0
 Url:            http://nedbatchelder.com/code/coverage/%{version}
 Summary:        Code coverage measurement for Python
@@ -26,19 +26,13 @@ Group:          Development/Languages/Python
 Source:         http://pypi.python.org/packages/source/c/coverage/coverage-%{version}.tar.gz
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 BuildRequires:  python3
+BuildRequires:  python3-2to3
 BuildRequires:  python3-devel
 BuildRequires:  python3-distribute
 BuildRequires:  python3-xml
-BuildRequires:	python3-2to3
 Requires:       python3-distribute
 Requires:       python3-xml
 
-%if 0%{?suse_version} <= 1140
-%{!?python3_sitearch: %global python3_sitearch %(python3 -c "from distutils.sysconfig import get_python_lib; print(get_python_lib(1))")}
-%{!?py3_ver: %global py3_ver %(python3 -c "import sys; version=str(sys.version_info[0]) + '.' + str(sys.version_info[1]); print(version)")}
-%endif
-Requires:       python(abi) = %{py3_ver}
-
 %description
 Coverage.py measures code coverage, typically during test execution. It uses
 the code analysis tools and tracing hooks provided in the Python standard
@@ -46,6 +40,7 @@ library to determine which lines are executable, and which have been executed.
 
 %prep
 %setup -q -n coverage-%{version}
+sed -i "s|coverage =|coverage-%{py3_ver} =|" setup.py # Add Python version suffix to binaries 
 
 %build
 2to3 --nobackups --write .
@@ -53,12 +48,11 @@ python3 setup.py build
 
 %install
 python3 setup.py install --prefix=%{_prefix} --root=%{buildroot}
-mv %{buildroot}%{_bindir}/coverage %{buildroot}%{_bindir}/coverage-python%{py3_ver}
 
 %files
 %defattr(-,root,root,-)
 %doc AUTHORS.txt CHANGES.txt README.txt
-%{_bindir}/coverage-python%{py3_ver}
+%{_bindir}/coverage-%{py3_ver}
 %{python3_sitearch}/coverage
 %{python3_sitearch}/coverage-%{version}-py%{py3_ver}.egg-info