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.

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

Tear httplib2 out of google-cloud #1998

Closed
dhermes opened this issue Jul 19, 2016 · 17 comments
Closed

Tear httplib2 out of google-cloud #1998

dhermes opened this issue Jul 19, 2016 · 17 comments
Assignees
Labels
api: core priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release.

Comments

@dhermes
Copy link
Contributor

dhermes commented Jul 19, 2016

I plan to tackle this soon-ish.

This is so we can move to a better-maintained (or allow BYO) transport layer.

@dhermes dhermes self-assigned this Jul 19, 2016
dhermes added a commit to dhermes/google-cloud-python that referenced this issue Sep 2, 2016
dhermes added a commit to dhermes/google-cloud-python that referenced this issue Sep 2, 2016
@theacodes
Copy link
Contributor

theacodes commented Dec 2, 2016

This should now be possible since oauth2client has been replaced with google-auth.

@dhermes
Copy link
Contributor Author

dhermes commented Dec 2, 2016

google.cloud.streaming needs fixin' first (I seem to recall @jonparrott volunteering for that one, but can't confirm it because our chat history gets deleted!)

@theacodes
Copy link
Contributor

Have we a bug for streaming?

My chat history gets deleted to prevent me from volunteering for dumb things.

@dhermes
Copy link
Contributor Author

dhermes commented Dec 2, 2016

I don't think so, it's part of the "ditch httplib2 bug"

@daspecster
Copy link
Contributor

@dhermes @jonparrott is google_auth_httplib2.py what should be used instead of directly using httplib2?

@theacodes
Copy link
Contributor

theacodes commented Mar 7, 2017 via email

@dhermes
Copy link
Contributor Author

dhermes commented Jun 27, 2017

Here is what remains:

@bmabey
Copy link

bmabey commented Jul 21, 2017

@dhermes Do you have a timeline for when this will be completed?

@dhermes
Copy link
Contributor Author

dhermes commented Jul 21, 2017

@bmabey Much closer right now (because #3555 is done, w00t!) then we were 24 days ago.

@theacodes theacodes changed the title Tear httplib2 out of gcloud.streaming Tear httplib2 out of google-cloud Jul 21, 2017
@theacodes theacodes self-assigned this Jul 21, 2017
@theacodes theacodes added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. and removed priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jul 21, 2017
@theacodes
Copy link
Contributor

I am bumping this to a p1 and assigning to myself, it's critical that we remove usage of httplib2 before we GA any more libraries.

@theacodes
Copy link
Contributor

/cc @lukesneeringer on that last comment.

@lukesneeringer
Copy link
Contributor

Copy that. Thank you for the effort.

@lukesneeringer
Copy link
Contributor

Note: Translate is NOT pushed to PyPI yet; do I need to hold it?

@theacodes
Copy link
Contributor

theacodes commented Jul 21, 2017

@lukesneeringer translate is probably okay. All of the other current GA libraries accept an http parameter that has to be an httplib2 instance, so I'm not sure how we want to deal with that yet.

Update: nvm, the _http parameter to client constructors is and has always been private and explicitly documented that we reserve the right to change it. I'm sure there are a handful of users out there specifying it, but they can pin versions until they're ready to switch.

@dhermes
Copy link
Contributor Author

dhermes commented Jul 27, 2017

Ahhhhhhh! 🙌 🎊 🥇 🎉 🌮

@tseaver
Copy link
Contributor

tseaver commented Jul 27, 2017

GOOOOOOOOOOOOOOOOOOOOOAL!!!

@daspecster
Copy link
Contributor

Congrats guys!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: core priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release.
Projects
None yet
Development

No branches or pull requests

6 participants