On 23 February 2017 at 08:36, Glyph Lefkowitz <glyph@twistedmatrix.com> wrote:
Go's build toolchain has many features worth envying but most of its advantages have to do with deployments _outside_ of containers, where you have to ship to customer environments with fraught and unknown system configurations. If you have any level of control over your deployment target, Go and, say, Python with PEX are ~equivalent .
I was going to chime in about pex earlier - but since you need to provide your own interpreter, I didn't think it solved his whole issue. Otherwise, pex is a great format for deploying python easily. At Twitter, we deployed the (Twisted) TweetDeck API using it for years, with a ton of dependencies, both c-libs and pure python. Really nice to be able to produce a deployable artefact, which can be hashed & stored for re-deploy later if needed (and ideally integration-tested & staged by passing different args on the cli).