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

Behavior changed when .coveragerc is missing #357

Closed
nedbat opened this issue Jan 31, 2015 · 1 comment
Closed

Behavior changed when .coveragerc is missing #357

nedbat opened this issue Jan 31, 2015 · 1 comment
Labels
bug Something isn't working

Comments

@nedbat
Copy link
Owner

nedbat commented Jan 31, 2015

Suppose you have no .coveragerc file.

In v3.7, if you constructed a coverage object like this: coverage(config_file=".coveragerc"), it would be OK with the file not existing.

In 4.0a4, if you construct a coverage object that way, it will raise an exception: CoverageException: Couldn't read '.coveragerc' as a config file. Constructing it with coverage(config_file=True) will work the same in both versions: it will be fine with the file not existing.

The nose-cov plugin uses cov_core, which always supplies a config_file option.

Should it always be OK for the specified config file to be missing? If the user uses coverage run --rcfile=xyzzy.ini, shouldn't it complain if that file doesn't exist?


@nedbat
Copy link
Owner Author

nedbat commented Feb 12, 2015

Fixed in 4e9a2f263d97 (bb).

@nedbat nedbat closed this as completed Feb 12, 2015
@nedbat nedbat added major bug Something isn't working labels Jun 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant