Packaging and deployment of standalone Python applications?
kawazu428 at gmail.com
Thu Sep 17 08:23:52 CEST 2015
and first off, thanks bunches for your comment.
Am 17.09.2015 um 00:19 schrieb Laura Creighton:
> Your problem is likely with the shared library search paths.
> Different distributions put them in different places. It's a real
> pain, and the reason why docker is getting more popular.
Well I thought something like this but then again wondered whether this
really would be the cause - after all, Thunderbird, Firefox, OpenOffice,
Java and a bunch of other applications that are available as "binary"
downloads for "generic Linux" do seem to work on RedHat/CentOS, Debian,
Ubuntu without these issues. Are these all statically built? Would this
be an option for distributing Python applications, as well?
Or, other option: Would it work to, say, use venv, make sure there
always is a Python of the same version on the target machine installed
(say 3.4), and then distribute "just" the python parts without including
the interpreter / binary itself?
Thanks in advance and all the best,
More information about the Python-list