Context Navigation

Changes between Version 3 and Version 4 of Ticket #3384

-                      v3
+                      v4
 For more context, the follow-up ticket to this would be #3385, which will attempt to use [[https://coveralls.io|coveralls.io]] for code coverage checks.  We are not entirely satisfied with [[https://codecov.io|codecov.io]], which we currently use.  For example, it is not always clear why codecov checks turn disapprove of certain PRs, even when test coverage remains unchanged.
+Now, in order to upload coverage reports to codecov.io, we will need to use [[https://github.com/coveralls-clients/coveralls-python|coveralls-python]], which requires that coverage reports should be in coverage 5.0 format.  Which is the real motivation for unpinning coverage.
+Now, in order to upload coverage reports to codecov.io, we will need to use [[https://github.com/coveralls-clients/coveralls-python|coveralls-python]], which requires that coverage reports should be in coverage 5.0 format.  Which is the real motivation for unpinning coverage.
+''If'' coveralls.io works better than codecov.io for us, we can switch to the former.  Even if it doesn't, this change does not affect codecov: codecov can continue working with the reports we submit in XML format.
 (See coverage [[https://coverage.readthedocs.io/en/coverage-5.2.1/changes.html#version-5-0a2-2018-09-03|changelog]]: "Coverage’s data storage has changed. In version 4.x, .coverage files were basically JSON. Now, they are SQLite databases.")