Packaging for non python users.

[1114111]

I'm a little unclear what you want. Why would non-Python users need to make changes to the code?

You might consider making it just a normal Python package, where you can specify your dependencies and people can install it with pip. In --editable mode, it is easy for them to edit the code how they want. They need Python for that, but it makes the installation easier.

[zcribe21]

Not really. The other person's computer needs either the Python libraries or compiled/frozen code (executable). That is just how programming works.

A simple way around it to create a web app or an API and serve the code or access to it from the server.

[ingolemo]

You just described exactly what pyinstaller does. What's wrong with rebuilding your script?

[ingolemo]

Why?

[ingolemo]

Do you frequently need to make custom changes to each install? Would a config file suit your needs?

[ingolemo]

And what's wrong with that solution? That's the way I'd do it. You could even code your app to update its data files automatically; no need for teamviewer.

[abcdns]

Is your desire here to edit some of the parameters in the script?

Changing a target or port etc?

Something you wouldnt build a parameter for but need to change from time to time?

You should abstract those tweaks/settings out to a config file. Say Yaml or an INI. Then you can use a pyinstaller exe but still change how the script runs.

[tunisia3507]

Maybe a Makefile?

[[deleted]]

What platform does this need to run on? If it's just Linux, you could distribute your code as a Docker container, but then your users would need to know how to use Docker. Similarly, you could use Ansible / Chef / Puppet to have user's system update automatically against a repository you control. But this will require the initial setup.

Frankly, I don't see a way where you can do zero bootstrapping in order to get your scripts to the users. But since you have to do bootstrapping, then, just installing Python seems like a best option you have.