ImageField.save should be documented upfront and obvious

[freyley]

Nowhere on this page

​http://docs.djangoproject.com/en/dev/ref/models/fields/

Does it say how to save an image to a filefield or imagefield. Only by digging in to the code was I able to find this:

p = Photo(...)
p.image.save(filename, ContentFile(data))

which was exactly what I wanted. If there's a preferred way to do it, that'd be fine too.

[Ramiro Morales]

(formatted description)

[Gabriel Hurley]

Added a patch that adds a large chunk to the FileField docs regarding the publicly available methods that get added by the complex machinations of FieldFile. Updates the ImageField docs as well to make it a little more obvious that it gets everything from FileField.

[Russell Keith-Magee]

The content of this patch is all good stuff, but the patch still needs work.

In particular, it is missing two things:

• A transition between the discussion about FileField, and the methods that are on FieldFile
• Corrections to the markup that suggest that open() et al are methods on FileField -- they're on FieldFile.

[Gabriel Hurley]

Updated patch for FileField/ImageField docs that include FieldFile information

[Gabriel Hurley]

Hopefully this addresses Russ' concerns above. It's a little tricky because even though the open, save, delete, etc. methods are in actuality on FieldFile, they are exposed on the FileField/ImageField instance itself. I tried to make this clear while still being technically accurate and adding a better logical separation.

[Russell Keith-Magee]

(In [13202]) Fixed #12229 -- Added documentation of the FieldFile methods that are exposed by FileField and ImageField. Thanks to Gabriel Hurley for the draft patch.

[Russell Keith-Magee]

(In [13203]) [1.1.X] Fixed #12229 -- Added documentation of the FieldFile methods that are exposed by FileField and ImageField. Thanks to Gabriel Hurley for the draft patch.

Backport of r13202 from trunk.

[Jacob]

Milestone 1.2 deleted