Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update coverage to 4.5 #24

Closed
wants to merge 1 commit into from
Closed

Conversation

pyup-bot
Copy link
Collaborator

@pyup-bot pyup-bot commented Feb 4, 2018

There's a new version of coverage available.
You are currently using 4.4.1. I have updated it to 4.5

These links might come in handy: PyPI | Changelog | Repo

Changelog

4.5


  • A new kind of plugin is supported: configurators are invoked at start-up to
    allow more complex configuration than the .coveragerc file can easily do.
    See :ref:api_plugin for details. This solves the complex configuration
    problem described in issue 563_.
  • The fail_under option can now be a float. Note that you must specify the
    [report] precision configuration option for the fractional part to be
    used. Thanks to Lars Hupfeldt Nielsen for help with the implementation.
    Fixes issue 631_.
  • The include and omit options can be specified for both the [run]
    and [report] phases of execution. 4.4.2 introduced some incorrect
    interactions between those phases, where the options for one were confused
    for the other. This is now corrected, fixing issue 621_ and issue 622_.
    Thanks to Daniel Hahler for seeing more clearly than I could.
  • The coverage combine command used to always overwrite the data file, even
    when no data had been read from apparently combinable files. Now, an error
    is raised if we thought there were files to combine, but in fact none of them
    could be used. Fixes issue 629_.
  • The coverage combine command could get confused about path separators
    when combining data collected on Windows with data collected on Linux, as
    described in issue 618_. This is now fixed: the result path always uses
    the path separator specified in the [paths] result.
  • On Windows, the HTML report could fail when source trees are deeply nested,
    due to attempting to create HTML filenames longer than the 250-character
    maximum. Now filenames will never get much larger than 200 characters,
    fixing issue 627_. Thanks to Alex Sandro for helping with the fix.

.. _issue 563: https://bitbucket.org/ned/coveragepy/issues/563/platform-specific-configuration
.. _issue 618: https://bitbucket.org/ned/coveragepy/issues/618/problem-when-combining-windows-generated
.. _issue 621: https://bitbucket.org/ned/coveragepy/issues/621/include-ignored-warning-when-using
.. _issue 622: https://bitbucket.org/ned/coveragepy/issues/622/report-omit-overwrites-run-omit
.. _issue 627: https://bitbucket.org/ned/coveragepy/issues/627/failure-generating-html-reports-when-the
.. _issue 629: https://bitbucket.org/ned/coveragepy/issues/629/multiple-use-of-combine-leads-to-empty
.. _issue 631: https://bitbucket.org/ned/coveragepy/issues/631/precise-coverage-percentage-value

.. _changes_442:

4.4.2


  • Support for Python 3.7. In some cases, class and module docstrings are no
    longer counted in statement totals, which could slightly change your total
    results.
  • Specifying both --source and --include no longer silently ignores the
    include setting, instead it displays a warning. Thanks, Lo茂c Dachary. Closes
    issue 265_ and issue 101_.
  • Fixed a race condition when saving data and multiple threads are tracing
    (issue 581_). It could produce a "dictionary changed size during iteration"
    RuntimeError. I believe this mostly but not entirely fixes the race
    condition. A true fix would likely be too expensive. Thanks, Peter Baughman
    for the debugging, and Olivier Grisel for the fix with tests.
  • Configuration values which are file paths will now apply tilde-expansion,
    closing issue 589_.
  • Now secondary config files like tox.ini and setup.cfg can be specified
    explicitly, and prefixed sections like [coverage:run] will be read. Fixes
    issue 588_.
  • Be more flexible about the command name displayed by help, fixing
    issue 600_. Thanks, Ben Finney.

.. _issue 101: https://bitbucket.org/ned/coveragepy/issues/101/settings-under-report-affect-running
.. _issue 581: https://bitbucket.org/ned/coveragepy/issues/581/race-condition-when-saving-data-under
.. _issue 588: https://bitbucket.org/ned/coveragepy/issues/588/using-rcfile-path-to-toxini-uses-run
.. _issue 589: https://bitbucket.org/ned/coveragepy/issues/589/allow-expansion-in-coveragerc
.. _issue 600: https://bitbucket.org/ned/coveragepy/issues/600/get-program-name-from-command-line-when

.. _changes_441:

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 馃

@pyup-bot pyup-bot mentioned this pull request Feb 4, 2018
@coveralls
Copy link

Coverage Status

Coverage remained the same at 96.281% when pulling 63c8a84 on pyup-update-coverage-4.4.1-to-4.5 into a59bd3f on master.

@pyup-bot
Copy link
Collaborator Author

Closing this in favor of #26

@pyup-bot pyup-bot closed this Feb 11, 2018
@sys-git sys-git deleted the pyup-update-coverage-4.4.1-to-4.5 branch February 11, 2018 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants