diff options
| author | Rapptz <[email protected]> | 2020-01-03 20:42:45 -0500 |
|---|---|---|
| committer | Rapptz <[email protected]> | 2020-01-03 20:42:45 -0500 |
| commit | 195b5188e8707d14d8b43aa31c3fc4628e0c370b (patch) | |
| tree | 5777933510c1e9ed089fbddf4fb1c0e51e5335f4 /docs | |
| parent | Document that widget members may be incomplete. (diff) | |
| download | discord.py-195b5188e8707d14d8b43aa31c3fc4628e0c370b.tar.xz discord.py-195b5188e8707d14d8b43aa31c3fc4628e0c370b.zip | |
Add Attachment.to_file to easily send an attachment.
The first thing someone will ask when someone sees this method is
"Why doesn't `send` just accept `Attachment`?". This question is fair
but it has an issue: exception propagation becomes confusing.
When we save a file and write it to memory an HTTP request is sent
similar to other API calls. Like all HTTP requests, these can fail.
Since these requests denote failure using HTTPException, if it were to
originate within `send` then it becomes confusing to know whether the
attachment saving itself failed or whether the sending failed.
For that reason, and to keep in-line with only 1 type of HTTP call per
method, it doesn't make sense for `send` to support `Attachment`.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions