> When I say build static like a Go binary, I mean that the binary contains everything, and is not allowed to dynamically load anything at all. Just code? Or a

> When I say build static like a Go binary, I mean that the binary contains everything, and is not allowed to dynamically load anything at all. Just code? Or are you talking about data (e.g. HTML files) too? A lot of python's ecosystem seems pretty built around the assumption that non-code assets won't be bundled into single files, so any magic single-file Python compiler would probably have to include the ability to distribute those assets separately with the executable. > preferrably it doesn't need a C standard library I don't believe that golang even meets this standard--not with default options, at least. Also, why? How often have dynamically linked libc version differences really been a challenge for you in production? > does system calls manually This is generally considered to be a bad idea. Golang has moved away from this on several platforms, and people are making noise about doing it on Linux, too. A minority of compiled languages opt to go to this route. Why do you want this?