In Python, virtual environments are used to isolate projects from each other (if they require different versions of the same library, for example). They let you install and manage packages without administrative privileges, and without conflicting with the system package manager. They also allow to quickly create an environment somewhere else with the same dependencies.

Virtual environments are a crucial tool for any Python developer. And at that, a very simple tool to work with.

Pipenv is a Python packaging tool that does one thing reasonably well — application dependency management. However, it is also plagued by issues, limitations and a break-neck development process. In the past, Pipenv’s promotional material was highly misleading as to its purpose and backers.

In this post, I will explore the problems with Pipenv. Was it really recommended by Can everyone — or at least, the vast majority of people — benefit from it?

(This post has been updated in February 2020 and May 2020 to reflect the current state of Pipenv.)

I used up 0.99 GB out of my 1 GB allowance. So, I had to buy some more. My (former) operator, Orange, sells a 1GB package for an ultra-low price (not really) of 15 PLN. (You can get the same package for less money, even half of that price, with other carriers.)

How to turn that on? You can send a text message or call a robot. I’ll give them a call then.