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.

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

Withdraw PEP 759 #4248

Merged
merged 4 commits into from
Jan 31, 2025
Merged

Withdraw PEP 759 #4248

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
124574a
Withdraw PEP 759
warsaw Jan 31, 2025
c4c4a3d
Fix lint problems, with one known exception
warsaw Jan 31, 2025
de5762f
Merge branch 'main' into warsaw/withdraw-759
warsaw Jan 31, 2025
6ca3bf9
Include resolution link
warsaw Jan 31, 2025
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
18 changes: 16 additions & 2 deletions peps/pep-0759.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,12 @@ Author: Barry Warsaw <[email protected]>,
Emma Harper Smith <[email protected]>
PEP-Delegate: Donald Stufft <[email protected]>
Discussions-To: https://discuss.python.org/t/pep-759-external-wheel-hosting/66458
Status: Draft
Status: Withdrawn
Type: Standards Track
Topic: Packaging
Created: 01-Oct-2024
Post-History:
Post-History: 10-Oct-2024, 31-Jan-2025
Resolution: `31-Jan-2025 <https://discuss.python.org/t/pep-759-external-wheel-hosting/66458/48>`__

Abstract
========
Expand All @@ -30,6 +31,19 @@ files affect the metadata returned for a package's :ref:`Simple Repository API
in both HTML and JSON formats, and how traditional wheels can easily be turned
into ``.rim`` files.

PEP withdrawn
=============

This PEP was withdrawn by the authors on 2025-01-31. Our reading of the sentiment in the discussion
thread is that, while the problems this PEP attempts to solve are valid, most folks would prefer a
different approach. Specifically, our read is that most users would prefer more control over the
ability to specify multiple indexes, how those indexes interoperate, and the priority and trust
assertions for those indexes. For example, solutions such as :pep:`766` may provide a better way
forward. Existing stop gap measures (e.g. PyPI limit increase requests and the `"wheel-stub"
<https://pypi.org/project/wheel-stub/>`_ approach) are sufficient -- if not ideal -- in the
meantime. The authors wish to thank everyone who contributed to the constructive discussion, and
especially those who showed their support for this PEP, both in public and private.

Rationale
=========

Expand Down