On Sun, 22 Nov 2020 at 11:32, Hartmut Goebel firstname.lastname@example.org wrote:
Am 20.11.20 um 11:01 schrieb Paul Moore:
- Add the ability for zipapp to prepend a launcher for Windows, so
zipapps can be built that "run natively" on Windows (Unix and MacOS don't need this, because for them, shebangs are handled by the OS, not by the language runtime). It *might* be possible to use the py.exe launcher, if not the sample code in the zipapp docs is probably sufficient. 2. Add something that makes writing MacOS "app bundles" from zipapps easier. That could be part of the zipapp module, or a standalone module.
So basically re-implement py2exe, py2app, PyInstaller, etc?!
Definitely not. I'm thinking of something *far* more limited. Specifically, things I'm not suggesting be in the stdlib:
1. Bundling the Python binaries. 2. Stripping out unneeded modules. 3. Executables forms other than "single file". 4. Support for C extensions.
I would be open to using the "embedded distribution" on Windows to ship such an executable with a dedicated Python interpreter, but unless CPython starts distributing an embedded distribution for other platforms, that's as far as I'd go.