From 21b1b1f02a6293f9b62c26c9b7ec2d2e3246ce89 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Filipe=20La=C3=ADns?= Date: Tue, 7 Apr 2026 01:27:05 +0100 Subject: [PATCH 1/2] PEP 739: specify how to handle conflicting installs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Filipe Laíns --- peps/pep-0739.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/peps/pep-0739.rst b/peps/pep-0739.rst index 2bf5039bcec..cb79720ebc6 100644 --- a/peps/pep-0739.rst +++ b/peps/pep-0739.rst @@ -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:: From b97169efe9aa342cf197bf7c99443b1a8776a6af Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Filipe=20La=C3=ADns?= Date: Tue, 19 May 2026 19:13:49 +0100 Subject: [PATCH 2/2] share -> MAY share MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Filipe Laíns --- peps/pep-0739.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/peps/pep-0739.rst b/peps/pep-0739.rst index cb79720ebc6..b3d2f403c3b 100644 --- a/peps/pep-0739.rst +++ b/peps/pep-0739.rst @@ -52,8 +52,8 @@ 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. +When multiple Python installations **MAY** 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.