"Gophers are better snakes and snakes are better turtles." Your phrasing is about is presumptuous and usually-not-true as mine.
Python (and Go) make for pretty terrible shell script replacements unless you're doing non-shell-style programming in Bash. Proper leveraging of Python's dynamic nature does make it quicker to write programs that don't require a high degree of safety, such as throwaway tools. A rapid, iterative write-test-repeat workflow in Python can make up for trivial coding errors in small and medium sized programs, often resulting in a quicker, if not hackier, time-to-completion than Go. It's more about that Python is a worse Go than it is about Go trying to be a better Python: large or long running programs are problematic in Python, because the comparatively unstructured style disfavors ease of automated test integration, and will often leave type errors lingering in rarely visited code paths, such that a Python service can fail after months on a simple error that a statically typed language would've caught at compile time. None of that means that Go is a better Python -- it just means that the situations which gave rise to that opinion were those in which Python was being employed in a capacity for which Go is much better suited.