On 22Nov2020 13:22, Steven D'Aprano
On Sun, Nov 22, 2020 at 12:56:01PM +1100, Cameron Simpson wrote:
On 21Nov2020 17:54, Chris Angelico
wrote: The range of people who (a) cannot install from PyPI and can only use the stdlib, and (b) cannot deploy with a .pyz and must deploy an .exe, is extremely narrow. In what situation do you have to make a native executable but cannot get a tool from PyPI to make one?
Well, for my personal example, an in house tool for an in house task, the users _can_ copy a Mac .app into their Applications folder. I _do not_ and would not expect them to (likely choice): - install macports or homebrew - install python - install source code and libraries (needed PyQt)
They're end users; some are (variously) technical and some aren't, but none should need to be technical. I want them to copy an app to a new machine and be happy - drag'n'drop a single thing.
Sure, but why does PyInstaller have to be in the std lib for you to support this use-case?
It doesn't. I'm not arguing for that; I'm at least slightly against it in fact. I'm _still_ arguing against Chris' apparent position that wanting to make a standalone bundle is pretty much a null situation. I think I've let his "attractive nuisance" description get under my skin. Still, as you say:
That was Chris' question: Under what circumstances does somebody have to make a native application but **cannot use one of the tools on PyPI to do it**? (Or the freeze tool.)
It is true that I, at least, am not in that position: needing to make a
standalone app and unable to access PyPI to get tools to build it.
I may have misconstrued Chris to mean my users rather than myself. (His
full question is still quoted at the top of this message for reference.)
And on that basis I withdraw my example.
But it definitely applies to my users: thier install process should be a
trivial copy-this-app experience. That does require a complete bundle.
Cheers,
Cameron Simpson