Use pycurl .whl for hub environment
#1047
Merged
+1
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you @jrdnbradford!!!!!! |
|
Thanks @minrk and @consideRatio for all the work on my group of PRs. You all are the best. 🥇 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use of
--no-binarywas required forpycurl7.45.3due to a wheel problem. Related issues:pycurlupdate causing "500 : Internal Server Error" after logging into newly created TLJHs using Google Authenticator oauthenticator#731pycurlupdate causing "500 : Internal Server Error" after logging into newly created TLJHs using Google Authenticator #964As of
7.45.4this was corrected, installing the latestpycurlfrom the wheel now works. This saves a non-negligible amount of time in CI actions, tests, and installation.