Seconded. I read this article and thought "nope, not touching any of those tools". I'd rather spend my time building products than spending a week researching the landscape of 10 different package management approaches.
Same. pip + virtualenv just works.
There are lots of errors when it comes to reproducing the build on other machines. Pip install -r requirements.txt does not guarantee that you will install the same version of packages on a new machine, and in fact, you will typically not.
I've never had problems with this when requirements.txt contains package versions
Have you, or are you not using explicit versions supplied by eg pip freeze?
Totally agree. And why not just invest time into pip than invent again.
Same. I feel people invent problems in order to not use these tools.