|
1 | | -PEP: 772 |
| 1 | +PEP: 773 |
2 | 2 | Title: A Python Installation Manager for Windows |
3 | 3 | Author: Steve Dower |
4 | 4 | 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. |
906 | 906 | This is much closer to the desired behaviour of the global ``python`` command |
907 | 907 | than any alternative. |
908 | 908 |
|
| 909 | +TODO: Note that this follows Gentoo's design as well |
| 910 | + |
909 | 911 |
|
910 | 912 | Replacing py.exe |
911 | 913 | ---------------- |
@@ -1112,6 +1114,8 @@ use it to install Python. The admin-only configuration described earlier in |
1112 | 1114 | attacker who can run PyManager is able to do whatever the user can do, and only |
1113 | 1115 | a complete application whitelisting approach can prevent the use of Python. |
1114 | 1116 |
|
| 1117 | +TODO: Notes about security of package acquisition (tl;dr: TLS) |
| 1118 | + |
1115 | 1119 | Runtime installs by PyManager are fully accessible by, and modifiable by, the |
1116 | 1120 | current user. This is equivalent to typical installs using the traditional |
1117 | 1121 | 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 |
1146 | 1150 | and normal compatibility processes. New functionality is based on the current |
1147 | 1151 | implementation, and not the original PEP text. |
1148 | 1152 |
|
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 |
1150 | 1154 | Systems"), and is believed to be consistent with it in devising an approach for |
1151 | 1155 | Windows that allows similar guidance to be given to users on all platforms. |
1152 | 1156 |
|
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 |
1154 | 1158 | registry"), and in fact improves our ability to follow it with a more flexible |
1155 | 1159 | system for registering our own runtimes. Tools that follow PEP 514 will find any |
1156 | 1160 | runtimes that choose to use the registration, regardless of how they were |
|
0 commit comments