I tried installing it in a virtualenv and then I saw it installed virtualenv inside the virtualenv, which is like virtualenv inception. I'm going to try it again tomorrow. I think the change of workflow will take some time to adapt for me. I weirdly like uninstalling everything in my virtualenv and then installing from scratch from my requirements.txt, and the reason behind that is I work on some projects that have a huge list of dependencies(far too many for my liking) and often a package gets out of date or can't install anymore or a certain bug only creeps in with a specific version of a package. Are there any tools out there for converting your requirements.txt to the format that pipenv uses?