don't want to start a programming language war here, but I have to object every single thing you wrote 😄

1. With Go you just need to do "go get" and stop. No need to do "go tidy" (unless you imported something that you don't want to use anymore), no need to care about GOHOME and, unless you need to do something unusual, no need to manually edit go.mod;

2. don't know what error about being deprecated you encountered, could you be more specific?

3. the point about deploy is not just related to be compiled. It is about HOW it is compiled, or better, linked. A Go binary is almost always a statically linked binary, that means that has no dependency on specific system library version. So I can compile my Go binary on the latest Fedora and deploy it on the oldest CentOS I still have in production. Also, I can cross compile to several architectures and OS without installing any external tool.

4. With python you have so many issues deploying a script. You have to care about:

a) the Python version because they break compatibility every time (Go never broke backward compatibility since it was release btw)

b) for every non trivial task in Python you need to have several system library installed, gcc, g++, a fortan compiler and god knows what else.

source: my pythonic collegues spend 10% of their time writing code and the rest trying to deploy it in production.