Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove dependencies on httplib2 and google-auth-httplib2 #1118

Open
hiranya911 opened this issue Dec 1, 2020 · 10 comments
Open

Remove dependencies on httplib2 and google-auth-httplib2 #1118

hiranya911 opened this issue Dec 1, 2020 · 10 comments
Labels
next major: breaking change this is a change that we should wait to bundle into the next major version type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Milestone
3.0.0

Comments

@hiranya911
Copy link

This library still has dependencies on httplib2 and google-auth-httplib2. Most of the other Google Python libs have migrated away from these. Specifically, httplib2 has known thread-safety problems, and google-auth-httplib2 seems to have been developed as a backward compat package. Are there any plans for migrating these dependencies out?
@yoshi-automation yoshi-automation added the triage me I really want to be triaged. label Dec 2, 2020
@parthea parthea added type: question Request for information or clarification. Not an issue. and removed triage me I really want to be triaged. labels Dec 2, 2020
@parthea parthea self-assigned this Dec 2, 2020
@busunkim96
Copy link
Contributor

Hi @hiranya911,

We're looking at putting something related to this (moving off of httplib2) on our 2021 Q1 OKRs. We'll update this issue when we have more concrete plans.

@hiranya911 hiranya911 mentioned this issue Dec 3, 2020
Closed
@parthea parthea removed their assignment Dec 4, 2020
@GabrieleCalarota
Copy link

Any update on this?
I'm having trouble with firebase send multicast message (SSL and thread safety of httplib2)

@busunkim96
Copy link
Contributor

This work was deprioritized in favor of investments on the modern google-cloud-* clients. @hiranya911 If you have issues from customers please do share them with us internally.

@hiranya911
Copy link
Author

Internal issue for future reference: 181689506

@parthea parthea mentioned this issue Jun 4, 2021
Closed
@parthea parthea added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. and removed type: question Request for information or clarification. Not an issue. labels Jun 4, 2021
@mroblesm
Copy link

mroblesm commented Jun 9, 2021

Is there any update on this issue? We use Google API Client to interact with Dataflow API, and couldn't find any reference to dataflow support on Google Cloud Client...

@parthea
Copy link
Contributor

parthea commented Jun 9, 2021 •
edited
Loading

Hi @mroblesm,

I've filed a bug internally to inquire about the status of a Google Cloud Client for dataflow. Googlers see b/190586207

@GabrieleCalarota
Copy link

Thanks for investigating guys! Very appreciated ;)

@taiki-okano
Copy link

taiki-okano commented Jul 2, 2021 •
edited
Loading

I think this issue is important.
I am using Google Drive API with this library, but when I try to copy a folder which contains multiple files, it is super slow.
Sometimes it takes about 5 minutes. So, I changed it to execute in parallel, but I needed to authenticate before every single request.

I hope geniuses in Google realize this issue and do something for this...

@GabrieleCalarota
Copy link

Any update on this?

@rkhwaja rkhwaja mentioned this issue Dec 31, 2022
Closed
@JoshuaFox JoshuaFox mentioned this issue Mar 12, 2023
Closed
@parthea parthea mentioned this issue Apr 18, 2023
Open
@parthea parthea added this to the 3.0.0 milestone Apr 18, 2023
@parthea parthea added the next major: breaking change this is a change that we should wait to bundle into the next major version label Apr 18, 2023
@parthea parthea self-assigned this Sep 26, 2023
@parthea parthea removed their assignment Nov 10, 2023
@ZupoLlask
Copy link

Any update on this? @dhermes @theacodes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
next major: breaking change this is a change that we should wait to bundle into the next major version type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
3.0.0
Development

No branches or pull requests
8 participants
@ZupoLlask @hiranya911 @mroblesm @parthea @busunkim96 @taiki-okano @GabrieleCalarota @yoshi-automation