Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PEP 668: Address feedback and mark as accepted #2673

Merged
merged 2 commits into from
Jun 27, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions pep-0668.rst
Original file line number Diff line number Diff line change
Expand Up @@ -9,13 +9,14 @@ Author: Geoffrey Thomas <geofft@ldpreload.com>,
Elana Hashman <ehashman@debian.org>,
Pradyun Gedam <pradyunsg@gmail.com>
PEP-Delegate: Paul Moore <p.f.moore@gmail.com>
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
========
Expand Down Expand Up @@ -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)
Expand Down Expand Up @@ -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
Expand Down