-
Notifications
You must be signed in to change notification settings - Fork 36
Work with coverage 4.x or 5.x #66
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
Conversation
|
I would be in favor of moving to a v2 plugin that supports:
To ease migration for others, I would advocate ensuring that v1 works with all those versions, and then that we drop support of previous versions of Python/Coverage/Django when we bump the major version of the plugin. |
|
@jambonrose sounds good to me. One reason I have heard for continuing to support Python 3.5: it's the version installed on a still-supported LTS of Ubuntu: 16.04. But I don't feel strongly about it. |
|
Also: I should add a supported way to get this information: coveragepy/coveragepy#920 |
|
I think the build should go green if you update the branch now. |
|
@nedbat : That's a good reason to support Python 3.5 . Additionally, I see now that Django 2.2 is also Python 3.5 compatible. |
|
Updated. |
browniebroke
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose we can now remove the restriction for <5 in setup.py?
|
@jambonrose Is this good to go? Do I merge, or do you? |
|
What's the time line on getting this merged? |
|
I will look at this tomorrow. Thanks all for your patience. Sent with GitHawk |
|
The test suit for this PR ran with Coverage 4.5.4 . I think we should:
Normally, I'd advocate for updating Tox to run both Coverage 4 and 5, but given our conversation about deprecation and the existing test run on Coverage 4, that feels unnecessary. |
|
I made those changes. |
@jambonrose This makes it work for both, though it's not nice. I wondered about mocking the creation of the plugins to track which had been made during the test, but I didn't quickly see a way to do that.
Also, I don't know if we should support 4.x and 5.x (which would double the already bulky list of tox environments), or just move to 5?