Never require 'body' for requests.

[busunkim96]

Fixes #713.

Never require that a body be passed in a request. Validation of body will be left to the server.

[busunkim96]

If you forget to pass a body to an API that has required properties, the server will throw an error.

Example:

(create requires a body with a new job as its payload.)

from googleapiclient.discovery import build

service = build('jobs', 'v2')
req = service.jobs().create()
resp = req.execute()

    raise HttpError(resp, content, uri=self.uri)
googleapiclient.errors.HttpError: <HttpError 400 when requesting https://jobs.googleapis.com/v2/jobs?alt=json returned "Following fields are missing or invalid: Company Name, Description, Title, Job Requisition ID, One of Application Method (URL/Emails/Instructions). (Possible reasons: non-numeric for double field, invalid language code, etc.). Request ID for tracking:

[TxBillbr]

How long will it take before this is visible to the client lib? Passing body={} in a request is very dangerous Python behavior. This broke a bunch of our automation.

[busunkim96]

@TxBillbr I'll cut a release today -- apologies for the disruption this caused!

[TxBillbr]

Thanks much for the prompt handling. I have just released a local work-around for our local library that tries the correct method and if it throws an error tries with the body={}.

[busunkim96]

@TxBillbr This is available in the latest release 1.7.10