3 ms·
Probably because it doesn't actually package the Python interpreter into the executable and relies on a hashbang (ie. `#!/bin/python`) to actually run the bundl
by packetlost 3y ago
Probably because it doesn't actually package the Python interpreter into the executable and relies on a hashbang (ie. `#!/bin/python`) to actually run the bundled source files. Pex [0] does the same thing.
It's a half solution at best, but if you control the infrastructure it does dramatically simplify things like Dockerfiles and other deployment stuff. Not super useful for general distribution IMO.
[0]: https://pex.readthedocs.io/en/v2.1.140/ https://pex.readthedocs.io/en/v2.1.140/
- totetsu 3y agoI ran into ssh cypher issues when I tried to share a packed python project. Worked on my machine but not my colleagues
- hackan 3y agoIt's a cool trick, I used it to pack a tool long time ago: https://github.com/HacKanCuBa/passphrase-py/blob/219d6374338ed9a1475b4f09b0d85212376f11e0/Makefile#L40 https://github.com/HacKanCuBa/passphrase-py/blob/219d6374338... Basically, u zip the package, then add the shebang on the zip binary. Quite cool and simple! No need for external tools :p
- yellowapple 3y agoThat's a bummer. An app being self-contained is kinda the point of an AppImage IMO, and depending on an external Python (if one even exists) throws a wrench in that.