Refer consistently to project as “Coverage”

[nedbat]

Originally reported by Ben Finney (Bitbucket: bignose, GitHub: bignose)

---

The documentation, messages, and comments have numerous inconsistent names for the Coverage system and project. I recommend to change all references to the project and system to use the name “Coverage”.

The names “coverage.py” and “Coverage.py” are obsolete – the code is not in a single file – and confusing, since ‘coverage.py’ strongly connotes a single module file.

The attached patch changes all references to the system and project to “Coverage”, which leaving unchanged the references to the commands, modules, and terminology.

---

• Bitbucket: https://bitbucket.org/ned/coveragepy/issue/275
• This issue had attachments: coveragepy.project-name.r1595.diff. See the original issue for details.

[nedbat]

Original comment by Ben Finney (Bitbucket: bignose, GitHub: bignose)

---

I see that a version 4.0 is coming up soon. Can we please use that opportunity to consistently use the name “Coverage”, or pick some other name and use it consistently?

[nedbat]

Thanks for the push. I've decided to use "coverage.py" consistently as the project name. True, there is no file named "coverage.py," but I am OK with that. "Coverage" is too vague all by itself.

Fixed in e6b27046afb3 (bb)