> 1) For performing the same task, Python's always much easier to
>     program. And easier algorithms mean less dark corners for bugs to
>     hide.

> 2) Python (and Perl, Ruby, Lua and Scheme) is already debugged and
>     secure. Without C's pointers, overflowable arrays, manual garbage
>     collection, matching of mallocs and frees, and other security
>     problems, one can write a secure Python program with a lot less
>     security knowledge.

> 3) Assuming your Python program doesn't import a bunch of seldom-used
>     Python libraries, deployment is*much*  easier. Deploying a
>     well-written Python program is a mere wget. I once had a distro with
>     a bad or missing youtube-dl package. Because it's just a python
>     script, I copied it from the Internet onto my path, and bang, I had
>     youtube-dl. Try that with any C program.

> 4) Python has several ways of invoking a binary program, so if one part
>     of the project absolutely requires C, that part can be a tiny C
>     program that's easy and secure to program, and have it called by
>     Python.

> 5) A lot of the functionality of a C program could be imitated by
>     existing POSIX tools like cat, grep, awk, sed, cut, sort, gzip, and
>     the like. Running these programs first, in order to cut way down on
>     the data transfer, can allow the stdout to go into a Python program
>     that can keep up with the process.