Re:Warp – self-contained, single binary applications
by paavoova on Friday October 12, 2018 @10:38PM
(#18206082)
Python can do something similar albeit far simpler via packaging as an executable zipfile. Just structure everything you need in a directory and zip up with __main__.py in the root. All resources are available as an in-memory binary stream, including individual source .py files. Of course if you want to package something like a C library, you need to unpack that to disk to be able to access it with ctypes.
[ Parent
| on HN ]
Re:Warp – self-contained, single binary applications
by stdclass on Saturday October 13, 2018 @02:13AM
(#18206691)
PHP has something similar, called .phar https://en.wikipedia.org/wiki/PHAR_(file_format)
Re:Warp – self-contained, single binary applications
by creatornator on Saturday October 13, 2018 @01:12AM
(#18206545)
Are you referring to the zipapp library? I had no idea this even existed until now but that seems pretty clever. Huh. Why can't it also dynamically unzip a shared object library?
Re:Warp – self-contained, single binary applications
by paavoova on Saturday October 13, 2018 @02:08AM
(#18206678)
You don't need to use any libraries, you can do something as simple as:
$ zip -r mymodule.zip mymodule/
$ echo '#!/usr/bin/env python3' > myapp
$ cat mymodule.zip >> myapp
$ chmod 755 myapp
The reason why you have to handle shared libraries and any other non-.py data yourself is because Python doesn't know what to do with it. You can access it as binary data via pkgutil.get_data(), but linking shared libraries is system-dependent and Python doesn't load them itself. As the dynamic linker can't find a shared library in a zip file, the only thing you can do is extract it separately. This is documented in https://docs.python.org/3/library/zipimport.html
Any files may be present in the ZIP archive, but only files .py and .pyc are available for import. ZIP import of dynamic modules (.pyd, .so) is disallowed.