From 94f4c4a682aa8ae1974a55711857a8d4cca315f6 Mon Sep 17 00:00:00 2001 From: Hugo Date: Wed, 12 Dec 2018 00:50:32 +1100 Subject: [PATCH] Apply suggestions from code review Minor edits Co-Authored-By: radarhere <3112309+radarhere@users.noreply.github.com> --- docs/reference/open_files.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reference/open_files.rst b/docs/reference/open_files.rst index 1ba546687..e439d8495 100644 --- a/docs/reference/open_files.rst +++ b/docs/reference/open_files.rst @@ -30,7 +30,7 @@ and may fail:: im5 = Image.open(f) im5.load() # FAILS, closed file -If a filename or a path-like object are passed to Pillow, then the resulting +If a filename or a path-like object is passed to Pillow, then the resulting file object opened by Pillow may also be closed by Pillow after the ``Image.Image.load()`` method is called, provided the associated image does not have multiple frames. @@ -56,9 +56,9 @@ Image Lifecycle memory. The image can now be used independently of the underlying image file. - If a filename or a path-like object were passed to ``Image.open()``, then + If a filename or a path-like object was passed to ``Image.open()``, then the file object was opened by Pillow and is considered to be used exclusively - by Pillow. So if the image is a single frame image, the file will + by Pillow. So if the image is a single-frame image, the file will be closed in this method after the frame is read. If the image is a multi-frame image, (e.g. multipage TIFF and animated GIF) the image file is left open so that ``Image.Image.seek()`` can load the appropriate frame.