Skip to content

PEP 739: specify how to handle conflicting installs #4889

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.

Sign up for GitHub

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

Draft
FFY00 wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

PEP 739: specify how to handle conflicting installs #4889

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
21b1b1f
PEP 739: specify how to handle conflicting installs
FFY00 Apr 7, 2026
b97169e
share -> MAY share
FFY00 May 19, 2026
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
8 changes: 8 additions & 0 deletions peps/pep-0739.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,14 @@ platform-independent standard library directory (``stdlib``, eg.
``/usr/lib/python3.14/build-details.json``), **UNLESS** unfeasible due to
technical limitations.

When multiple Python installations share the same prefix, to resolve conflicts,
distributors should prepend an extension to the file — eg.
``build-details.XXX.json``, ``build-details.YYY.json``, etc.
The extension text is determined by the distributor, but it **SHOULD** indicate
the difference(s) between the installations — eg.
``build-details.x86_64-free-threading.json``,
``build-details.arm64_v8a-free-threading.json``,
``build-details.x86_64.json``, etc.

.. attention::

Expand Down
Loading