-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Release PR: pip 20.0 #7619
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
Release PR: pip 20.0 #7619
Conversation
Looks like the Windows CI failed to checkout a git commit, after building the distributions properly. I don't think there's much point in exploring this right now but we should look into this at a later time. For now, I'll go ahead with the rest of the do-the-release tasks.
|
Line ending issue? Why are we running these steps under git bash? That sounds risky, as it's a msys (cygwin-like) environment and could well behave differently than "native" Windows. (I don't necessarily think that's the issue here, I just dislike using msys/cygwin as a general rule). |
I think this release has issue.
Is it intended that both |
This comment has been minimized.
This comment has been minimized.
@pradyunsg Looking at this issue, I'm pretty sure it is a line ending issue.
It looks like this was an unintended consequence of #7600. That PR was addressing people running with the unusual setting of I haven't been able to recreate the issue locally, yet, as it needs a combination of a Unix machine and a Windows one, and I don't have a Unix VM set up right now. But I'm pretty sure the analysis above is accurate. |
Ok, great; it's exactly what I thought it was -- a non-critical failure due to some interaction of Windows+git+CI on newlines. :) #7600 was squash merged, so anyone who wants to file a PR reverting it only needs to do |
Setting per-repository config (and reverting the changes in the Nox script) sounds like a good solution to me. I’m guessing it would also benefit #7617 as well. Continuing the discussion there. |
Filing this PR as a sanity check to make sure that the CI passes with the version bumped.
It contains the commit that'll be tagged as
20.0
-- don't merge this unless you're @pradyunsg.