File tree Expand file tree Collapse file tree 1 file changed +19
-2
lines changed Expand file tree Collapse file tree 1 file changed +19
-2
lines changed Original file line number Diff line number Diff line change 1
1
PEP: 778
2
2
Title: Supporting Symlinks in Wheels
3
- Author: Ethan Smith <ethan@ethanhs.me >
3
+ Author: Emma Harper Smith <emma@python.org >
4
4
Sponsor: Barry Warsaw <barry@python.org>
5
5
PEP-Delegate: Paul Moore <p.f.moore@gmail.com>
6
- Status: Draft
6
+ Discussions-To: https://discuss.python.org/t/pep-778-supporting-symlinks-in-wheels/53824
7
+ Status: Deferred
7
8
Type: Standards Track
8
9
Topic: Packaging
9
10
Requires: 777
10
11
Created: 18-May-2024
12
+ Post-History: `10-Oct-2024 <https://discuss.python.org/t/pep-778-supporting-symlinks-in-wheels/53824 >`__
11
13
12
14
Abstract
13
15
========
@@ -17,6 +19,21 @@ installed. To properly handle distributing libraries in wheels, we propose a new
17
19
metadata file to handle symlinks in a platform portable manner. This specification requires
18
20
a new wheel major version, discussed in :pep: `777 `.
19
21
22
+ PEP Defferal
23
+ ============
24
+
25
+ This PEP has been deferred until a better compatibility story for major changes to the wheel
26
+ format is established. Once a compatibility story is established for wheels which allows backwards
27
+ incompatible behavior in an unobtrusive way, the following points should be addressed in this PEP:
28
+
29
+ - Re-focus topic to just symliinks for shared libraries on Unix platforms. Perhaps tie to
30
+ platform tags?
31
+ - Should the symlinks be materialized as file attributes in the archive or a ``LINKS `` file?
32
+ Could it be encoded in ``RECORD ``?
33
+ - Clarify that this PEP is insufficient to be useful for PEP 660 editable installs since it will no
34
+ longer be cross platform.
35
+ - Describe fallback behavior in instances where symlinks are unavailable on Unix platforms.
36
+
20
37
Motivation
21
38
==========
22
39
You can’t perform that action at this time.
0 commit comments