Disable body parameter in HTTPException constructor

[asvetlov]

Now the exception can be created with either body or text.
It over complicates things in a light of removing inheritance from web.Response.

Let's deprecate body before changing the inheritance hierarchy.

[aio-libs-bot]

GitMate.io thinks possibly related issues are #593 (Add charset parameter to web.Response constructor), #1992 ([enhancement] Add ability to disable automatic decompression of body), #193 (Should aiohttp.web.Response accept body as positional parameter?), #2067 (Disable Cookie Handling), and #2262 (Disable DNS cache).

[eirnym]

Does it mean, that I can't send back a binary here? I have a requirement to communicate using binary protocol and this change is breaking my ability to use exceptions

[kxepal]

Why do you need to use exceptions for such communication?

[eirnym]

I don't need to check very-special-values when return from the function and able to throw an HTTP error.
Such exceptions in aiohttp and other frameworks (including other languages) are used interchangeable with Response objects to indicate an HTTP error in more clear way than using plain Response object. aiohttp is not an exception to this.

I agree, that not every http response require/accept a body at all.

[eirnym]

In my case I want to provide client with some additional contextual information where the error occurred.