[mtrn]

Shipping python projects isn't easy. Even if you have a prefect package on pypi, that specifies its dependencies, it may conflict with other tools using other versions of those libraries.

Compiling python does not feel right.

Using native packages is better[1], but you have to plan it out. You can package virtualenvs into native packages[2] - and this is probably the most solid way, but you'll need packaging setups for various package managers.

In short, "written in Go" for me means with a high probability, just run "go get x" - or download a binary.

Since we are at it, I'd love to hear about better shipping strategies for Python projects.

[1] https://hynek.me/talks/python-deployments/ [2] https://labs.spotify.com/2013/10/10/packaging-in-your-packag...

[est]

> In short, "written in Go" for me means with a high probability, just run "go get x" - or download a binary.

Then you have to install & compile `go get` first, no?

[lqdc13]

When you mean shipping, do you mean deploying production apps to the cloud or just downloading/using top-like tools as a user?

I thought we were just talking about resource monitoring something. I think deployment is a totally separate subject. But for a top-like Python tool, I really like "glances". It has way more features than this Go version.

But regarding deployments, everything works if you make your own pip packages stored locally for your project. That way if it works on your clean VM, it works when you push to the cloud.