Copied images are not associated with the original file

This commit is contained in:
Andrew Murray 2021-10-16 21:32:27 +11:00
parent fa53b71afe
commit fa74f2272b

View File

@ -47,6 +47,10 @@ Image Lifecycle
memory. The image can now be used independently of the underlying memory. The image can now be used independently of the underlying
image file. image file.
Any Pillow method that creates a new image instance based on another will
internally call ``load()`` on the original image and then read the data.
The new image instance will not be associated with the original image file.
If a filename or a ``Path`` object was passed to ``Image.open()``, then the If a filename or a ``Path`` object was passed to ``Image.open()``, then the
file object was opened by Pillow and is considered to be used exclusively by 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 be closed in Pillow. So if the image is a single-frame image, the file will be closed in