DatuX

Thats indeed a nice tool. I'll try to figure out if i can generate it automatically for each release via github, so we can have a direct-download link in the...

@DvdGiessen yes i think its a good idea to add documentation for that. However this is different from the zipapp method mentioned above: pyinstaller will actually create a binary which...

@lciti i get this: ``` psy@ws1 ~/zfs_autobackup % ./zfs-autobackup Traceback (most recent call last): File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main return _run_code(code, main_globals, None, File "/usr/lib/python3.8/runpy.py", line 87, in _run_code...

If i change some stuff and remove all the "zfs_autobackup." prefixes from the imports it works, but then it wont function as a proper python module anymore..sigh.. If somebody knows...

I think its this problem: https://bugs.python.org/issue26277

I wasted several hours on this. If someone wants to fix it, create a PR. I cant get it so that zfs_autobackup is both a standaard python 2 and 3...

I tried your changes to no avail: ``` psy@ws1 ~/zfs_autobackup % python3 -m zipapp zfs_autobackup -p "/usr/bin/env python3" -o zfs-autobackup ; ./zfs-autobackup Traceback (most recent call last): File "/usr/lib/python3.8/runpy.py", line...

I've made the wrong assumption that the directory structure would be temp/*.py instead it should temp/zfs_autobackup/*.py and then its fine. (doh)

Sorry no news yet, first have to finish zfs-autoverify/zfs-check, after that i'll look into it. @neodc what if you create a venv outside the container and use that inside the...

3.2-beta1 will be released soon, its safe to use. :) Edwin