Set httplib2.RETRIES to 1.

[Ali Afshar, 2012-12-07 19:02:56]

https://codereview.appspot.com/6906051/diff/2001/apiclient/discovery.py
File apiclient/discovery.py (right):

https://codereview.appspot.com/6906051/diff/2001/apiclient/discovery.py#newco...
apiclient/discovery.py:63: httplib2.RETRIES = 1
Not saying it is wrong, but why did you decide on 1?

[jcgregorio_google, 2012-12-07 19:07:53]

https://codereview.appspot.com/6906051/diff/2001/apiclient/discovery.py
File apiclient/discovery.py (right):

https://codereview.appspot.com/6906051/diff/2001/apiclient/discovery.py#newco...
apiclient/discovery.py:63: httplib2.RETRIES = 1
On 2012/12/07 19:02:56, Ali Afshar wrote:
> Not saying it is wrong, but why did you decide on 1?

It's the safest option, particularly for APIs where requests may be tied to
money, for example, a request to kick off an expensive set of work in BigQuery.

[Ali Afshar, 2012-12-07 19:09:56]

On 2012/12/07 19:07:53, jcgregorio_google wrote:
> https://codereview.appspot.com/6906051/diff/2001/apiclient/discovery.py
> File apiclient/discovery.py (right):
> 
>
https://codereview.appspot.com/6906051/diff/2001/apiclient/discovery.py#newco...
> apiclient/discovery.py:63: httplib2.RETRIES = 1
> On 2012/12/07 19:02:56, Ali Afshar wrote:
> > Not saying it is wrong, but why did you decide on 1?
> 
> It's the safest option, particularly for APIs where requests may be tied to
> money, for example, a request to kick off an expensive set of work in
BigQuery.

Ok, understood, but hopefully a failed request doesn't cost the user money in
that case.

LGTM, any documentation on how to change the value?

[jcgregorio_google, 2012-12-07 19:18:51]

On 2012/12/07 19:09:56, Ali Afshar wrote:
> On 2012/12/07 19:07:53, jcgregorio_google wrote:
> > https://codereview.appspot.com/6906051/diff/2001/apiclient/discovery.py
> > File apiclient/discovery.py (right):
> > 
> >
>
https://codereview.appspot.com/6906051/diff/2001/apiclient/discovery.py#newco...
> > apiclient/discovery.py:63: httplib2.RETRIES = 1
> > On 2012/12/07 19:02:56, Ali Afshar wrote:
> > > Not saying it is wrong, but why did you decide on 1?
> > 
> > It's the safest option, particularly for APIs where requests may be tied to
> > money, for example, a request to kick off an expensive set of work in
> BigQuery.
> 
> Ok, understood, but hopefully a failed request doesn't cost the user money in
> that case.
> 
> LGTM, any documentation on how to change the value?

No docs changes, I think this actually fixes a bug in that
people probably presume that the underlying request is
only tried once. If someone wanted multiple retries it should
probably be done at a higher level with exponential back-off.

Committed in
http://code.google.com/p/google-api-python-client/source/detail?r=ab28805189b...