chore: update to using importlib.metadata for entry_points

Author: henryiii

source/conf.py

@@ -393,8 +393,8 @@
 nitpick_ignore = [
     ('envvar', 'PATH'),
     ('py:func', 'find_packages'),
-    ('py:func', 'pkg_resources.iter_entry_points'),
     ('py:func', 'setup'),
+    ('py:func', 'importlib.metadata.entry_points'),  # remove when 3.10 is released
     ('py:func', 'setuptools.find_namespace_packages'),
     ('py:func', 'setuptools.find_packages'),
     ('py:func', 'setuptools.setup'),

source/guides/creating-and-discovering-plugins.rst

@@ -136,17 +136,19 @@ in its :file:`setup.py`:
     )
 
 Then you can discover and load all of the registered entry points by using
-:func:`pkg_resources.iter_entry_points`:
+:func:`importlib.metadata.entry_points` (or the `backport`_
+``importlib_metadata >= 3.6`` for Python 3.6-3.9):
 
 .. code-block:: python
 
-    import pkg_resources
+    import sys
+    if sys.version_info < (3, 10):
+        from importlib_metadata import entry_points
+    else:
+        from importlib.metadata import entry_points
+
+    discovered_plugins = entry_points(group='myapp.plugins')
 
-    discovered_plugins = {
-        entry_point.name: entry_point.load()
-        for entry_point
-        in pkg_resources.iter_entry_points('myapp.plugins')
-    }
 
 In this example, ``discovered_plugins`` would be:
 
@@ -160,7 +162,9 @@ In this example, ``discovered_plugins`` would be:
     flexible and has a lot of options. It's recommended to read over the entire
     section on `entry points`_.
 
-.. _Setuptools: http://setuptools.readthedocs.io
+.. _Setuptools: https://setuptools.readthedocs.io
 .. _special support:
 .. _entry points:
-    http://setuptools.readthedocs.io/en/latest/setuptools.html#dynamic-discovery-of-services-and-plugins
+    https://setuptools.readthedocs.io/en/latest/setuptools.html#dynamic-discovery-of-services-and-plugins
+.. _backport: https://importlib-metadata.readthedocs.io/en/latest/
+

source/specifications/entry-points.rst

@@ -18,10 +18,10 @@ example:
 
 The entry point file format was originally developed to allow packages built
 with setuptools to provide integration point metadata that would be read at
-runtime with ``pkg_resources``. It is now defined as a PyPA interoperability
+runtime with ``importlib.metadata``. It is now defined as a PyPA interoperability
 specification in order to allow build tools other than setuptools to publish
-``pkg_resources`` compatible entry point metadata, and runtime libraries other
-than ``pkg_resources`` to portably read published entry point metadata
+``importlib.metadata`` compatible entry point metadata, and runtime libraries other
+than ``importlib.metadata`` to portably read published entry point metadata
 (potentially with different caching and conflict resolution strategies).
 
 Data model