From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Wed, 7 Nov 2018 18:30:31 +0000 (-0800)
Subject: glob uses fnmatch.filter instead of fnmatch since 2001. (GH-10102)
X-Git-Tag: v2.7.16rc1~86
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=322f8bc68cf3333db53882261fdebef0044b71e6;p=thirdparty%2FPython%2Fcpython.git

glob uses fnmatch.filter instead of fnmatch since 2001. (GH-10102)

(cherry picked from commit ae31e3fbf4e7def772fc1c94342d1011424fdc99)

Co-authored-by: Andrés Delfino <adelfino@gmail.com>
---

diff --git a/Doc/library/fnmatch.rst b/Doc/library/fnmatch.rst
index 42bbf7452fe7..8618f5f4a9a4 100644
--- a/Doc/library/fnmatch.rst
+++ b/Doc/library/fnmatch.rst
@@ -36,7 +36,7 @@ For example, ``'[?]'`` matches the character ``'?'``.
 
 Note that the filename separator (``'/'`` on Unix) is *not* special to this
 module.  See module :mod:`glob` for pathname expansion (:mod:`glob` uses
-:func:`fnmatch` to match pathname segments).  Similarly, filenames starting with
+:func:`.filter` to match pathname segments).  Similarly, filenames starting with
 a period are not special for this module, and are matched by the ``*`` and ``?``
 patterns.