Merge pull request #6099 from radarhere/pixels

Document alternatives to accessing individual pixels

docs/reference/PixelAccess.rst

@@ -6,7 +6,13 @@
 The PixelAccess class provides read and write access to
 :py:class:`PIL.Image` data at a pixel level.
 
-.. note::  Accessing individual pixels is fairly slow. If you are looping over all of the pixels in an image, there is likely a faster way using other parts of the Pillow API.
+.. note:: Accessing individual pixels is fairly slow. If you are
+          looping over all of the pixels in an image, there is likely
+          a faster way using other parts of the Pillow API.
+
+          :mod:`~PIL.Image`, :mod:`~PIL.ImageChops` and :mod:`~PIL.ImageOps`
+          have methods for many standard operations. If you wish to perform
+          a custom mapping, check out :py:meth:`~PIL.Image.Image.point`.
 
 Example
 -------
@@ -39,7 +45,7 @@ Access using negative indexes is also possible.
 
 
 :py:class:`PixelAccess` Class
------------------------------------
+-----------------------------
 
 .. class:: PixelAccess
 

docs/reference/PyAccess.rst

@@ -7,8 +7,12 @@
 The :py:mod:`~PIL.PyAccess` module provides a CFFI/Python implementation of the :ref:`PixelAccess`. This implementation is far faster on PyPy than the PixelAccess version.
 
 .. note:: Accessing individual pixels is fairly slow. If you are
-           looping over all of the pixels in an image, there is likely
-           a faster way using other parts of the Pillow API.
+          looping over all of the pixels in an image, there is likely
+          a faster way using other parts of the Pillow API.
+
+          :mod:`~PIL.Image`, :mod:`~PIL.ImageChops` and :mod:`~PIL.ImageOps`
+          have methods for many standard operations. If you wish to perform
+          a custom mapping, check out :py:meth:`~PIL.Image.Image.point`.
 
 Example
 -------