Big fan of Kenneth's work. One thing that surprised me about pipenv though is the slugified virtualenv name. I work on many virtualenvs a day and keep them all

Big fan of Kenneth's work. One thing that surprised me about pipenv though is the slugified virtualenv name. I work on many virtualenvs a day and keep them all in ~/.virtualenv/, no .env in the project, I use tree, and like code and artifacts to be seperate, and the dev environment to mirror deploy as closely as a I can. spacemacs loads them from there, my deploy mirrors this, and I use systemd units that use the absolute path on the target platform. easy to use, easy to explain. pipenv does not support this workflow though, something I thought was quite common. Suggestions to allow this to be optional does not seem to be well received https://github.com/pypa/pipenv/issues/589#issuecomment-330713212 https://github.com/pypa/pipenv/issues/589#issuecomment-33071... Maybe this is due to resourcing and will be fixed in time. For now, I just use pipenv for dependency management, and still use virtualenv like before. I would have liked to just use the one tool, but as it stands pipenv unfortunately is not a one stop shop for me - I really hope one day it will be.