* status: new => closed
* resolution: => invalid
Comment:
I don't see anything confusing in this docs.
> This made me assume that the file given via the file pointer will be
accessible via the keyword `fred`.
Docs explicitly states that the name `attachment` here is not relevant.
`fred` is not a keyword but a value for the `name` and it's used that way
in other examples.
> What I don't understand is why the keyword 'name' is there, and why
doesn't it simply say something like:
IMO it's valuable to show that other fields are handled properly and you
don't need to send files separately.
--
Ticket URL: <https://code.djangoproject.com/ticket/33757#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by bastian-wattro):
> Docs explicitly states that the name attachment here is not relevant.
See that is what confuses me. `attachment` is very relevant, as it is the
keyword in the FILES dict.
This is implicitly stated ("use whatever name your file-processing code
expects") but not clear if you jump in the docs without context
information.
--
Ticket URL: <https://code.djangoproject.com/ticket/33757#comment:5>