-
Notifications
You must be signed in to change notification settings - Fork 3k
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
remove should_use_ephemeral_cache #7268
remove should_use_ephemeral_cache #7268
Conversation
b41f949
to
234f1e9
Compare
234f1e9
to
cdf09bf
Compare
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.
The refactoring in wheel
looks good to me. Regarding the tests - do we have coverage on these cases elsewhere (like in integration tests) to ensure that we don't get unnoticed regressions?
I've been extra careful to cover all previous test cases of Regarding integration tests, I found this one that exercises caching: pip/tests/functional/test_install.py Lines 1179 to 1185 in 76a8954
I suppose there are plenty of integration tests for BTW, are there instructions to run tests with coverage? I could not immediately succeed at running |
Not that I've found - we still need some work in this area to ensure
If there's not one already we can make an issue to track that activity. |
I don't think there's one for tracking that. It's a good idea to do so, and based on my past preliminary investigation, there's support for subprocesses in coverage? Maybe we can use that? |
@chrahunt tests with |
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.
This reads much more clearly to me, and I think we have enough coverage with our integration tests that the loss of some of the overlapping behavior expressed in the removed unit tests is OK.
Thank you as always. :) |
Well it's not much compared to the tremendous work you and other pip maintainers accomplish. So thank your for that, as always too :) |
follow-up to #7262, towards #6852
A simple refactoring, no behavior change.