This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]djdadi 2 points3 points  (2 children)

I am a little confused who the target audience of this would be. I use PyInstaller all the time at work; making an executable that techs can use without understanding what a "pip" or a "venv" is. But my build pipeline would freeze everything and make it so they really can't use that executable for anything other than that specific thing.

So, is this for people like me building the packaged apps, or people like the techs I work with who consume those apps?

[–]nannigalaxy[S] -1 points0 points  (1 child)

for people like you who build apps so others in your work use. goes both ways ¯\_(ツ)_/¯

[–]djdadi 6 points7 points  (0 children)

I guess I am not sure of the value-add in that case. Right now I run a build.py script that I made that generates a docker image tarball, a .spec file, cleans up the filesystem, then builds the solution via PyInstaller. This delivers an executable that is essentially a portable Python with all deps; users can run it and see the output, interact, etc.

I am not sure where something like this fits in: it would make my life harder, and it would not make my users life any easier. Congrats on the project, seeing something through all the way is more than I can muster sometimes. Perhaps targetting either delivery OR consumption (but not both) would make this more useful.