-
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 emphasise, HTTPClient #276
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.
Fixes this warning: ../CHANGELOG.rst:24: WARNING: 'any' reference target not found: treq.testing
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.
Thank you! I am happy we are moving the "official recommendation" to a more explicit API.
One small suggestions, but looks ok to me!
docs/api.rst
Outdated
@@ -6,6 +6,11 @@ This page lists all of the interfaces exposed by the `treq` package. | |||
Making Requests | |||
--------------- | |||
|
|||
The :py:mod:`treq` module provides several shortcut functions for making |
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.
Would "convenience" be a better word here (and below) than "shortcut"?
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.
Sure, that makes sense to me.
Thank you for the review, @moshez! |
This is #129 merged forward.