Python Environment
Man it&#x27;s frustrating to see this comic and read the comments here, because it&#x27;s all so true. Python, in its noble quest for backwards compatibility, has accumulated so many different ways of packaging, distributing and installing libraries and apps that it&#x27;s rivaling Google&#x27;s chat apps.<p>Pipenv is the most promising solution <i>today</i> but is still very, very new. It&#x27;s modeled after yarn and has been officially blessed as &quot;The One True Way&quot; of installing stuff by the Python documentation. It has a way to go still to be as good as yarn (especially in terms of speed). The Python ecosystem has never had proper declarative packages like package.json (setup.cfg can be used to have fully declarative package metadata, but I seem to be the only one using it that way), which is a problem for package managers.<p>To those suggesting it, Docker is great but you&#x27;re still dealing with a package manager inside Docker, so that&#x27;s a moot point. It avoids the need for virtualenv, kind of, but so does pipenv and it does so more reliably and reproducibly (pipenv implements lockfiles).