Skip to content

Commit

Permalink
Explain use of saver='string' in iris.save (#3062)
Browse files Browse the repository at this point in the history
  • Loading branch information
pp-mo authored and pelson committed Jun 18, 2018
1 parent dbe1bc3 commit 220c272
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions lib/iris/io/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -346,11 +346,12 @@ def save(source, target, saver=None, **kwargs):
Kwargs:
* saver - Optional. Specifies the save function to use.
* saver - Optional. Specifies the file format to save.
If omitted, Iris will attempt to determine the format.
This keyword can be used to implement a custom save
format. Function form must be:
If a string, this is the recognised filename extension
(where the actual filename may not have it).
Otherwise the value is a saver function, of the form:
``my_saver(cube, target)`` plus any custom keywords. It
is assumed that a saver will accept an ``append`` keyword
if it's file format can handle multiple cubes. See also
Expand Down

0 comments on commit 220c272

Please sign in to comment.