2014-11-11 13:33:52 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Sun Nov 09 23:03:00 UTC 2014 - Led <ledest@gmail.com>
|
|
|
|
|
|
|
|
- fix bashism in pre script
|
|
|
|
|
2014-05-08 12:05:41 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Thu May 8 11:37:39 UTC 2014 - toddrme2178@gmail.com
|
|
|
|
|
|
|
|
- update to 3.7.1:
|
|
|
|
- Improved the speed of HTML report generation by about 20%.
|
|
|
|
- Fixed the mechanism for finding OS-installed static files for the HTML report
|
|
|
|
so that it will actually find OS-installed static files.
|
|
|
|
|
2013-10-24 13:40:59 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Thu Oct 24 13:40:56 UTC 2013 - speilicke@suse.com
|
|
|
|
|
|
|
|
- Require python-setuptools instead of distribute (upstreams merged)
|
|
|
|
|
2013-10-21 12:30:35 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Mon Oct 21 12:17:02 UTC 2013 - dmueller@suse.com
|
|
|
|
|
|
|
|
- update to 3.7:
|
|
|
|
* Added the ``--debug`` switch to ``coverage run``. It accepts a list of
|
|
|
|
options indicating the type of internal activity to log to stderr.
|
|
|
|
* Running code with ``coverage run -m`` now behaves more like Python does,
|
|
|
|
setting sys.path properly, which fixes `issue 207`_ and `issue 242`_.
|
|
|
|
* Coverage can now run .pyc files directly, closing `issue 264`_.
|
|
|
|
|
|
|
|
Over 15 other bugfixes, see included CHANGELOG
|
|
|
|
|
2013-05-15 14:48:13 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Wed May 15 14:50:46 UTC 2013 - speilicke@suse.com
|
|
|
|
|
|
|
|
- Fix update-alternatives and support upgrade from previous versions
|
|
|
|
|
2013-05-03 09:14:06 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Fri May 3 09:15:27 UTC 2013 - speilicke@suse.com
|
|
|
|
|
|
|
|
- Apply update-alternatives for binaries and man-pages
|
|
|
|
- Drop buildrequires on python-xml, I don't see it being used
|
|
|
|
|
2013-05-02 09:11:59 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Mon Apr 29 11:55:07 UTC 2013 - dmueller@suse.com
|
|
|
|
|
|
|
|
- update to 3.6:
|
|
|
|
* Fix Nose support
|
|
|
|
* Add --fail-under
|
|
|
|
* Over 20 bug fixes, for details see included CHANGELOG
|
|
|
|
|
- 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
2012-11-20 18:20:40 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Tue Nov 20 18:15:53 UTC 2012 - saschpe@suse.de
|
|
|
|
|
|
|
|
- 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
|
|
|
|
if the filename seems like maybe it wasn't meant to be Python. This is a
|
|
|
|
pragmatic fix for issue 82_.
|
|
|
|
+ The -m switch on coverage report, which includes missing line numbers
|
|
|
|
in the summary report, can now be specifed as show_missing in the
|
|
|
|
config file. Closes issue 173_.
|
|
|
|
+ When running a module with coverage run -m <modulename>, certain details
|
|
|
|
of the execution environment weren't the same as for
|
|
|
|
python -m <modulename>. This had the unfortunate side-effect of making
|
|
|
|
coverage run -m unittest discover not work if you had tests in a
|
|
|
|
directory named "test". This fixes issue 155_.
|
|
|
|
+ Now the exit status of your product code is properly used as the process
|
|
|
|
status when running python -m coverage run .... Thanks, JT Olds.
|
|
|
|
+ When installing into pypy, we no longer attempt (and fail) to compile
|
|
|
|
the C tracer function, closing issue 166_.
|
|
|
|
|
2012-05-24 14:07:00 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Thu May 24 11:47:40 UTC 2012 - cfarrell@suse.com
|
|
|
|
|
|
|
|
- license update: BSD-2-Clause and (GPL-2.0+ or MIT)
|
|
|
|
__init__.py is the only file with a definitive license statement
|
|
|
|
(BSD-2-Clause). Also, package contains jquery components (GPL-2.0+ or
|
|
|
|
MIT)
|
|
|
|
|
2012-05-23 15:41:38 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Wed May 23 07:30:26 UTC 2012 - highwaystar.ru@gmail.com
|
|
|
|
|
|
|
|
- python3 package added
|
|
|
|
- minor spec improvement (files section)
|
|
|
|
|
2012-03-10 16:54:12 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Sat Mar 10 16:54:01 UTC 2012 - saschpe@gmx.de
|
|
|
|
|
|
|
|
- Simplify macro usage
|
|
|
|
|
2011-11-10 11:12:30 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Thu Nov 10 11:11:58 UTC 2011 - saschpe@suse.de
|
|
|
|
|
|
|
|
- Update to version 3.5.1:
|
|
|
|
* The [paths] feature unfortunately didn't work in real world situations
|
|
|
|
where you wanted to, you know, report on the combined data. Now all paths
|
|
|
|
stored in the combined file are canonicalized properly.
|
|
|
|
|
2011-09-27 08:33:34 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Tue Sep 27 08:32:20 UTC 2011 - saschpe@suse.de
|
|
|
|
|
|
|
|
- Add python-distribute runtime requirement
|
|
|
|
|
2011-09-08 14:33:29 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Thu Sep 8 15:43:42 UTC 2011 - saschpe@suse.de
|
|
|
|
|
|
|
|
- Update to version 3.5.1b1:
|
|
|
|
* for-else constructs are understood better, and don't cause erroneous partial
|
|
|
|
branch warnings. Fixes issue 122.
|
|
|
|
* Branch coverage for with statements is improved, fixing issue 128.
|
|
|
|
* The number of partial branches reported on the HTML summary page was
|
|
|
|
different than the number reported on the individual file pages. This is
|
|
|
|
now fixed.
|
|
|
|
* An explicit include directive to measure files in the Python installation
|
|
|
|
wouldn't work because of the standard library exclusion. Now the include
|
|
|
|
directive takes precendence, and the files will be measured. Fixes
|
|
|
|
issue 138.
|
|
|
|
* The HTML report now handles Unicode characters in Python source files
|
|
|
|
properly. This fixes issue 124 and issue 144. Thanks, Devin
|
|
|
|
Jeanpierre.
|
|
|
|
* In order to help the core developers measure the test coverage of the
|
|
|
|
standard library, Brandon Rhodes devised an aggressive hack to trick Python
|
|
|
|
into running some coverage code before anything else in the process.
|
|
|
|
See the coverage/fullcoverage directory if you are interested.
|
|
|
|
...see CHANGES.txt for more
|
|
|
|
- Spec file cleanup:
|
|
|
|
* Use python-distribute instead of python-setuptools
|
|
|
|
* Changed license to BSD-3-Clause (SPDX style)
|
|
|
|
|
2011-05-06 12:44:31 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Fri May 6 12:32:26 UTC 2011 - saschpe@suse.de
|
|
|
|
|
|
|
|
- Update to version 3.4:
|
|
|
|
+ The XML report is now sorted by package name, fixing issue 88.
|
|
|
|
+ Programs that exited with sys.exit() with no argument weren't handled
|
|
|
|
properly, producing a coverage.py stack trace. That is now fixed.
|
|
|
|
- Changes from version 3.3.1:
|
|
|
|
+ Using parallel=True in .coveragerc file prevented reporting, but now does
|
|
|
|
not, fixing issue 49.
|
|
|
|
+ When running your code with "coverage run", if you call sys.exit(),
|
|
|
|
coverage.py will exit with that status code, fixing issue 50.
|
|
|
|
- Added documentation (AUTHORS.txt, CHANGES.txt and README.txt)
|
|
|
|
- Addded changes file
|
|
|
|
|
|
|
|
-------------------------------------------------------------------
|
|
|
|
Sat Aug 22 12:00:00 UTC 2009 - cfarrell1980@gmail.com
|
|
|
|
|
|
|
|
- Require setuptools
|
|
|
|
|
|
|
|
-------------------------------------------------------------------
|
|
|
|
Thu May 28 12:00:00 UTC 2009 - cfarrell1980@gmail.com
|
|
|
|
|
|
|
|
- Initial import
|
|
|
|
|