PEP 668: Address feedback and mark as accepted (#2673)

Author: pradyunsg

pep-0668.rst

@@ -9,13 +9,14 @@ Author: Geoffrey Thomas <[email protected]>,
         Elana Hashman <[email protected]>,
         Pradyun Gedam <[email protected]>
 PEP-Delegate: Paul Moore <[email protected]>
-Discussions-To: https://discuss.python.org/t/graceful-cooperation-between-external-and-python-package-managers-pep-668/10302
-Status: Draft
+Discussions-To: https://discuss.python.org/t/10302
+Status: Accepted
 Type: Informational
 Topic: Packaging
 Content-Type: text/x-rst
 Created: 18-May-2021
 Post-History: 28-May-2021
+Resolution: https://discuss.python.org/t/10302/44
 
 Abstract
 ========
@@ -293,9 +294,9 @@ Case Description                       ``pip install`` permitted   Deleting exte
 3    Distro Python in venv             Currently yes; stays yes    There are no externally-installed packages
 4    Distro Python in venv             Currently yes; stays yes    Currently no; stays no
      with ``--system-site-packages``
-5    Distro Python in Docker           Currently yes; stays yes    Currently yes; becomes no
-                                       (assuming the Docker image
-                                       removes the marker file)
+5    Distro Python in Docker           Currently yes; becomes no    Currently yes; becomes no
+                                       (assuming the distro
+                                       adds a marker file)
 6    Conda environment                 Currently yes; stays yes    Currently yes; stays yes
 7    Dev-facing distro                 Currently yes; becomes no   Currently often yes; becomes no
                                        (assuming they add a        (assuming they configure ``sysconfig`` as needed)
@@ -712,7 +713,8 @@ scheme but is still on ``sys.path``.
 The other is to arrange for the default ``sysconfig`` scheme to change
 when running inside a package build versus when running on an
 installed system. The ``sysconfig`` customization hooks from
-bpo-43976_ should make this easy: make your packaging tool set an
+bpo-43976_ should make this easy (once accepted and implemented):
+make your packaging tool set an
 environment variable or some other detectable configuration, and
 define a ``get_preferred_schemes`` function to return a different
 scheme when called from inside a package build. Then you can use ``pip