This repository has been archived by the owner on Sep 14, 2020. It is now read-only.
[272] Enforce the version of coverage
manually (pip fails to resolve)
#274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolve
coveralls
vs.pytest-cov
battle forcoverage
versions due tocoverage==5.0
release 2 days ago.Description
coverage==5.0
has been release on 14.12.2019 (2 days ago). This broke the CI/CD, as pip cannot resolve the version conflict:pytest-cov
wantscoverage>=4.4
, and is executed first.coverage==5.0
is found and installed.coveralls
wantscoverage<5.0
, but it is too late to reinstall.The fix is to install
coverage<5.0
before any of the dependencies request it. The solution is temporary by its nature. See #273 for a more generic approach (version pinning and auto-upgrading) — will be done somewhen later.Types of Changes