[issue28247] Add an option to zipapp to produce a Windows executable

Paul Moore added the comment: While I can see your point, I'm a little skeptical that anyone who's able to write C source code and compile it can't work out how to combine two binary files... :-) -- ___ Python tracker

[issue28247] Add an option to zipapp to produce a Windows executable

Ismail Donmez added the comment: The documentation helped a lot, so thanks for that! But it misses the final crucial step: copy /b zastub.exe+app.pyz app.exe The documentation talks about prepending the zastub.exe to the zip file but never mentions how, which is very confusing. --

[issue28247] Add an option to zipapp to produce a Windows executable

Change by Cheryl Sabella : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue28247] Add an option to zipapp to produce a Windows executable

miss-islington added the comment: New changeset 47a0e64ccf711e8d6d0c497d565ca7e2e82de7d4 by Miss Islington (bot) in branch '3.6': bpo-28247: Document Windows executable creation in zipapp (GH-6158)

[issue28247] Add an option to zipapp to produce a Windows executable

miss-islington added the comment: New changeset a70b8f593657f563116001f654587620271eb9ae by Miss Islington (bot) in branch '3.7': bpo-28247: Document Windows executable creation in zipapp (GH-6158)

[issue28247] Add an option to zipapp to produce a Windows executable

Change by miss-islington : -- pull_requests: +5920 ___ Python tracker ___

[issue28247] Add an option to zipapp to produce a Windows executable

Change by miss-islington : -- pull_requests: +5919 ___ Python tracker ___

[issue28247] Add an option to zipapp to produce a Windows executable

Paul Moore added the comment: New changeset 4be79f29463f632cd8b48486feadc2ed308fb520 by Paul Moore (Cheryl Sabella) in branch 'master': bpo-28247: Document Windows executable creation in zipapp (GH-6158)

[issue28247] Add an option to zipapp to produce a Windows executable

Cheryl Sabella added the comment: Hi Paul, Thanks for your response. I've made the pull request from your patch, so it would great if you could review it. Thanks! -- ___ Python tracker

[issue28247] Add an option to zipapp to produce a Windows executable

Change by Cheryl Sabella : -- pull_requests: +5915 ___ Python tracker ___ ___

[issue28247] Add an option to zipapp to produce a Windows executable

Paul Moore added the comment: Hi Cheryl, Looks like I dropped the ball on this one :-( I think it just needs to be applied to the main branch (3.7/3.8) - I don't think it's worth backporting. I'll try to get to it when I can, but it may not be for a few weeks, as I have

[issue28247] Add an option to zipapp to produce a Windows executable

Cheryl Sabella added the comment: Hi Paul, Were you interested in moving forward with this doc change? -- nosy: +csabella ___ Python tracker

[issue28247] Add an option to zipapp to produce a Windows executable

Brett Cannon added the comment: Only backport if you want; it's not a bug fix so technically it doesn't need to be backported. -- ___ Python tracker ___

[issue28247] Add an option to zipapp to produce a Windows executable

Paul Moore added the comment: OK, here's a first draft documentation patch. As it's purely a documentation change, I guess it should go into the 3.5, 3.6 and trunk branches? For now it's against trunk (it's not like that file has changed recently anyway), and I'll sort out the merge dance

[issue28247] Add an option to zipapp to produce a Windows executable

Brett Cannon added the comment: I think documentation is definitely the cheapest option. It's also the most flexible since if we find out there's a lot of usage of the guide then we can add explicit support. -- ___ Python tracker

[issue28247] Add an option to zipapp to produce a Windows executable

Paul Moore added the comment: I'm still unsure whether this would be a good idea. On the plus side, it provides (in conjunction with the "embedded" distribution) a really good way of producing a standalone application on Windows. On the minus side there are some limitations which may trip up

[issue28247] Add an option to zipapp to produce a Windows executable

Changes by Brett Cannon : -- nosy: +brett.cannon ___ Python tracker ___ ___

[issue28247] Add an option to zipapp to produce a Windows executable

Eryk Sun added the comment: Specifically, while CreateProcess does execute batch scripts via the %ComSpec% interpreter, the only extension it infers is ".exe". To run a ".cmd" or ".bat" file, you have to use the full name with the extension. -- nosy: +eryksun

[issue28247] Add an option to zipapp to produce a Windows executable

Paul Moore added the comment: (1) It starts an extra process (unless you're running the application from cmd.exe) and (2) in some cases, the system won't recognise a cmd file as an executable. For a simple example, t.cmd: @echo Hello from t example.py: from subprocess import run run(["t")]

[issue28247] Add an option to zipapp to produce a Windows executable

Serhiy Storchaka added the comment: Why not just change the extension to cmd and add the following line at the start? @python -x "%0" %* -- nosy: +serhiy.storchaka ___ Python tracker

[issue28247] Add an option to zipapp to produce a Windows executable

New submission from Paul Moore: The zipapp module allows users to bundle their application as a single file "executable". On Windows, the file is given a ".pyz" extension which is associated with the Python launcher. However, this approach is not always equivalent to a native executable (see