-
Notifications
You must be signed in to change notification settings - Fork 276
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
More porting from requests to urllib3 #2773
Open
jku
wants to merge
4
commits into
theupdateframework:develop
Choose a base branch
from
jku:no-requests
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
This comment was marked as outdated.
This comment was marked as outdated.
This was referenced Jan 31, 2025
This is related to theupdateframework#2762 (that replaces RequestsFetcher with Urllib3Fetcher) and takes care of the remaining requests use cases in the code base. Signed-off-by: Jussi Kukkonen <[email protected]>
This also removes RequestsFetcher from tuf.ngclient.__init__.py: Otherwise we can't drop the requests dependency. This means RequestsFetcher is not currently public. Signed-off-by: Jussi Kukkonen <[email protected]>
RequestsFetcher should still be public (even if deprecated). * We don't want to import RequestsFetcher in __init__ (because that requires importing requests) * but we do want RequestsFetcher to be importable publicly Move both fetchers out of _internal: that was never the right place for them anyway: they are public modules. Signed-off-by: Jussi Kukkonen <[email protected]>
@NicholasTanz GitHub doesn't let me mark you as reviewer but I wouldn't mind if you did review: this is a followup on your PR |
This was referenced Feb 14, 2025
NicholasTanz
approved these changes
Feb 15, 2025
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 looked over the codebase, and it seems that there are no more uses of requests
, and the changes look good to me 👍
Signed-off-by: Jussi Kukkonen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a followup to #2762 (that replaces RequestsFetcher with Urllib3Fetcher):
tuf.ngclient._internal
totuf.ngclient
: this was always the intention anyway and this allows RequestsFetcher to be not imported by default but importable if users want it:from tuf.ngclient.requests_fetcher import RequestsFetcher
This is pretty nice:
two dependencies!
Obviously if you install cryptography you end up with a few more but even in that case we have come down from 17 dependencies in v0.14 to five dependencies in next release. With this trajectory we're hitting zero before 2028!