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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update coverage to 5.0.3 #254

Merged
merged 1 commit into from
Jan 13, 2020
Merged

Conversation

pyup-bot
Copy link
Contributor

This PR updates coverage from 5.0.2 to 5.0.3.

Changelog

5.0.3

----------------------------

- A performance improvement in 5.0.2 didn't work for test suites that changed
directory before combining data, causing "Couldn't use data file: no such
table: meta" errors (`issue 916`_).  This is now fixed.

- Coverage could fail to run your program with some form of "ModuleNotFound" or
"ImportError" trying to import from the current directory. This would happen
if coverage had been packaged into a zip file (for example, on Windows), or
was found indirectly (for example, by pyenv-virtualenv).  A number of
different scenarios were described in `issue 862`_ which is now fixed.  Huge
thanks to Agbonze O. Jeremiah for reporting it, and Alexander Waters and
George-Cristian Bîrzan for protracted debugging sessions.

- Added the "premain" debug option.

- Added SQLite compile-time options to the "debug sys" output.

.. _issue 862: https://github.com/nedbat/coveragepy/issues/862
.. _issue 916: https://github.com/nedbat/coveragepy/issues/916


.. _changes_502:
Links

@coveralls
Copy link

Coverage Status

Coverage remained the same at 87.803% when pulling 96ec6dd on pyup-update-coverage-5.0.2-to-5.0.3 into e583b83 on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 87.803% when pulling 96ec6dd on pyup-update-coverage-5.0.2-to-5.0.3 into e583b83 on master.

@nikolas nikolas merged commit 703cf02 into master Jan 13, 2020
@ndittren ndittren deleted the pyup-update-coverage-5.0.2-to-5.0.3 branch October 7, 2022 17:24
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.

3 participants