#30466: FieldFile.save documentation is misleading
-------------------------------+--------------------------------------
     Reporter:  gcbirzan       |                    Owner:  nobody
         Type:  Bug            |                   Status:  closed
    Component:  Documentation  |                  Version:  2.2
     Severity:  Normal         |               Resolution:  wontfix
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+--------------------------------------
Changes (by Carlton Gibson):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 I think this is quite clear as is. (Or at least clear enough given the
 depth of the domain, and the link to the Managing files guide.)

 You're expected to read the whole thing. The terms are introduced and then
 explained as it goes along.

 If it were the other way round I think it would engender **more**
 confusion:

 > - "What's a django.core.files.File`?"
 > - "Well it's an object containing the file's contents... — but let's dig
 more."

 At that point the linked Managing files docs are worth a read.

 Happy to look at concrete suggestions but...

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30466#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.46076760298548e9d2d04e64b71fe8bb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to