bpo-34977: Add Windows App Store package#10245
Conversation
|
For anyone looking at the change, once you get past |
|
|
|
|
|
|
|
|
|
For anyone looking at the change, once you get past |
|
|
|
|
|
|
|
|
The main addition of this PR is the
PC/layoutscript that is basically a "make install" equivalent for Windows. It is able to include/exclude a range of components, and has the following output formats:To make the app store package work properly, I needed to add a new version of
python[w].exethat can correctly locate itself. To link to embedded scripts (pipandidle), this new launcher can also handle being renamed and will launch those modules instead. It also sets some environment variables to help pip always install to user site packages and keep those in an accessible location - it would be nice (but not essential) to set these defaults in other ways, but this is most reliable right now.To make venv work I modified the launcher to be able to launch the correct
python[w].exefrom a venv, so we no longer need to copy any other binaries into the Scripts directory. For recent releases of pip, this also works for launchers, but the embedded version of pip is too old.This is very close, but not quite yet ready to merge. Open to suggestions/changes here. For early releases, I'm planning to backport to a branch of 3.7 so we can put out 3.7.1 (hopefully) and also be able to run it against a 3.7 build, hopefully without having to backport too much. I've already obtained the PSF publisher on the store, and have checked that ownership/access can be transferred easily.
Can anyone think of anything I've missed?
https://bugs.python.org/issue34977