-
Notifications
You must be signed in to change notification settings - Fork 140
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
Mention, and emphasize, HTTPClient
in the documentation
#129
Conversation
Glyph pointed out that the various treq request functions (`treq.get()`, `treq.post()`, etc.) don't need to be modified. Instead, the documentation should suggest that you use a `treq.client.HTTPClient` instance directly if you need to customize its behavior. This reverts commit 972b84f.
…client.HTTPClient` is meant to be used.
This object is roughly analogous to request's |
@dreid That's a very good point. |
This would be useful to https://github.com/brettcannon/gidgethub/blob/master/gidgethub/treq.py |
What's blocking this now? Renaming the API might be an improvement but it doesn't seem like the best thing to block documenting the existing API on that. Once the documentation lands it will be trivial to update it to follow any renaming. |
@exarkun Really just the conflicts (and presumably a review); it looks like some other improvements have landed in the meanwhile, so the conflicts aren't totally trivial? |
Rather than encouraging people to mess around with
agent=
in the treq signature.This is a continuation of @cwaldbieser's work from #109 .