> All you're doing is hiding the call to system/execve behind deeper layers of abstraction. Thats the point, layers where environment variables do not pass - s

> All you're doing is hiding the call to system/execve behind deeper layers of abstraction. Thats the point, layers where environment variables do not pass - since they in that abstraction do not make sense. > Plus if people actually went ahead and reproduced all of the GNU/busybox toolchain inside of Python Basically all of gnu coreutils/busybox, is already inside python, its called import os. For your rsync example, python-librsync exists. C library, with python binding/interface. No need to run a bash to use the algorithm. If you still want to exec it, then use pythons binding to exceve system call or similar, not to system. I didnt suggest never to use execve and/or system, I said do not ever use system, sometimes highly questionably use execve.