If I understood it well, does this allow to create an executable file for python file that, even if built on windows, can run on mac, linux, whatever.... right?
in this way i can share my python code as an exe file that "not expert" can simply use by executing them on their machine, even if they don't have python installed... right?
I'm wondering if this can work inside a docker container: at the moment I develop every project inside a docker container, each with its requirements.txt. file.
Can I run this "pyapp" inside the docker (so Linux env) to create the exe file?
You would have to compile the binary on the target platform. Eventually I will support cross compiling but even then there will still be one binary for every platform/architecture pair.
Comments
Hi! It seems great!
If I understood it well, does this allow to create an executable file for python file that, even if built on windows, can run on mac, linux, whatever.... right?
in this way i can share my python code as an exe file that "not expert" can simply use by executing them on their machine, even if they don't have python installed... right?
I'm wondering if this can work inside a docker container: at the moment I develop every project inside a docker container, each with its requirements.txt. file.
Can I run this "pyapp" inside the docker (so Linux env) to create the exe file?
Have I understood it well?
Thanks very much!
You would have to compile the binary on the target platform. Eventually I will support cross compiling but even then there will still be one binary for every platform/architecture pair.
Hi! Thanks for the answer! Regarding the other points that I've written instead, are they correct? Thanks
Yes if you want to build the binaries in containers you could mount a directory where the artifacts should go.