Although, it makes me even more confused as to why they used python for the official client.
I can't speak exactly to why Python was chosen, but it should be noted this isn't intended to be the be-all-end-all in terms of clients. There are already a number of other independent clients that have been developed for various different purposes.
Not to mention python is on pretty much every platform in existence by default.
If you're expecting this as a global binary like you would in go there's no reason you can't just "pip install letsencrypt"...
...except needing docker and everything running it in a docker container entails over a simple CLI.
Also, it looks like they say "for god's sake don't pip install":
Please do not use python setup.py install or ``sudo pip install`. Those mode of operation might corrupt your operating system and is not supported by the Let’s Encrypt team! https://letsencrypt.readthedocs.org/en/latest/using.html#ins...
> python is on pretty much every platform in existence by default.
....except Windows? Which also doesn't support docker.
So the actual problem you have is that you selected an operating system that has zero native support for interpreted languages, and you're mad that they didn't cater their software to you?
(Seriously, though, VBscript, JScript and VBA are natively supported through WSH on Windows)
> Why python for the client software if you obviously already have Go experience in-house? Using python means you have to run all this virtual-env crap in a bash script, apt-get install a bunch of crap for setup and not support Windows. Seems like using (nearly) dependency-free Go application for the client as well would have been a no brainer. Was it just a case of having more access to python devs, or were there other technical reasons? Anyone know? I bet this has been asked before, but not turning anything up with google.
wow what's going on here? Auto comment robot gone wrong?