4
4
Emma Harper Smith <
[email protected] >
5
5
PEP-Delegate: Donald Stufft <
[email protected] >
6
6
Discussions-To: https://discuss.python.org/t/pep-759-external-wheel-hosting/66458
7
- Status: Draft
7
+ Status: Withdrawn
8
8
Type: Standards Track
9
9
Topic: Packaging
10
10
Created: 01-Oct-2024
11
- Post-History:
11
+ Post-History: 10-Oct-2024, 31-Jan-2025
12
+ Resolution: `31-Jan-2025 <https://discuss.python.org/t/pep-759-external-wheel-hosting/66458/48 >`__
12
13
13
14
Abstract
14
15
========
@@ -30,6 +31,19 @@ files affect the metadata returned for a package's :ref:`Simple Repository API
30
31
in both HTML and JSON formats, and how traditional wheels can easily be turned
31
32
into ``.rim `` files.
32
33
34
+ PEP withdrawn
35
+ =============
36
+
37
+ This PEP was withdrawn by the authors on 2025-01-31. Our reading of the sentiment in the discussion
38
+ thread is that, while the problems this PEP attempts to solve are valid, most folks would prefer a
39
+ different approach. Specifically, our read is that most users would prefer more control over the
40
+ ability to specify multiple indexes, how those indexes interoperate, and the priority and trust
41
+ assertions for those indexes. For example, solutions such as :pep: `766 ` may provide a better way
42
+ forward. Existing stop gap measures (e.g. PyPI limit increase requests and the `"wheel-stub"
43
+ <https://pypi.org/project/wheel-stub/> `_ approach) are sufficient -- if not ideal -- in the
44
+ meantime. The authors wish to thank everyone who contributed to the constructive discussion, and
45
+ especially those who showed their support for this PEP, both in public and private.
46
+
33
47
Rationale
34
48
=========
35
49
0 commit comments