summaryrefslogtreecommitdiff
path: root/Doc/tutorial
diff options
context:
space:
mode:
authorAndrés Delfino <34587441+andresdelfino@users.noreply.github.com>2018-04-21 09:17:26 -0300
committerSerhiy Storchaka <storchaka@gmail.com>2018-04-21 15:17:26 +0300
commitb81ca28b378c8b29204a37f8bd433a3379f53f7d (patch)
tree1139c5fc0e468a45ed7583ad8b8b2e9104183690 /Doc/tutorial
parent441d945eb33f8dc130b268ebfa11315b98a2433c (diff)
downloadcpython-git-b81ca28b378c8b29204a37f8bd433a3379f53f7d.tar.gz
bpo-33297: Mention Pillow to work with more image formats. (#6505)
Also update PIL doc references to Pillow.
Diffstat (limited to 'Doc/tutorial')
-rw-r--r--Doc/tutorial/modules.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/tutorial/modules.rst b/Doc/tutorial/modules.rst
index 584d4fd72e..3f689327a0 100644
--- a/Doc/tutorial/modules.rst
+++ b/Doc/tutorial/modules.rst
@@ -382,7 +382,7 @@ module names". For example, the module name :mod:`A.B` designates a submodule
named ``B`` in a package named ``A``. Just like the use of modules saves the
authors of different modules from having to worry about each other's global
variable names, the use of dotted module names saves the authors of multi-module
-packages like NumPy or the Python Imaging Library from having to worry about
+packages like NumPy or Pillow from having to worry about
each other's module names.
Suppose you want to design a collection of modules (a "package") for the uniform