Skip to content

Commit 55d5380

Browse files
committed
Add some self-notes
1 parent d9736cf commit 55d5380

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

peps/pep-0772.rst

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
PEP: 772
1+
PEP: 773
22
Title: A Python Installation Manager for Windows
33
Author: Steve Dower
44
Discussions-To: https://discuss.python.org/t/77900/
@@ -906,6 +906,8 @@ launches the most appropriate version of Python available on the user's machine.
906906
This is much closer to the desired behaviour of the global ``python`` command
907907
than any alternative.
908908

909+
TODO: Note that this follows Gentoo's design as well
910+
909911

910912
Replacing py.exe
911913
----------------
@@ -1112,6 +1114,8 @@ use it to install Python. The admin-only configuration described earlier in
11121114
attacker who can run PyManager is able to do whatever the user can do, and only
11131115
a complete application whitelisting approach can prevent the use of Python.
11141116

1117+
TODO: Notes about security of package acquisition (tl;dr: TLS)
1118+
11151119
Runtime installs by PyManager are fully accessible by, and modifiable by, the
11161120
current user. This is equivalent to typical installs using the traditional
11171121
installer or a Nuget package, but is more vulnerable to tampering than a Store
@@ -1146,11 +1150,11 @@ are already considered final, and the launcher is defined by its documentation
11461150
and normal compatibility processes. New functionality is based on the current
11471151
implementation, and not the original PEP text.
11481152

1149-
This proposal has no impact on :pep`394` ("The “python” Command on Unix-Like
1153+
This proposal has no impact on :pep:`394` ("The “python” Command on Unix-Like
11501154
Systems"), and is believed to be consistent with it in devising an approach for
11511155
Windows that allows similar guidance to be given to users on all platforms.
11521156

1153-
This proposal has no impact on :pep`514` ("Python registration in the Windows
1157+
This proposal has no impact on :pep:`514` ("Python registration in the Windows
11541158
registry"), and in fact improves our ability to follow it with a more flexible
11551159
system for registering our own runtimes. Tools that follow PEP 514 will find any
11561160
runtimes that choose to use the registration, regardless of how they were

0 commit comments

Comments
 (0)