@tecoholic I don't see that option going anywhere (pipenv is only for "programs", you still need pip for packaging libraries)
@meejah I should have been more clear. Packages are something I can live with using requirements.txt. It's the pipfile and lock file strategy from the pip env that gives me a headache. With virtualenv I knew everything was inside the project, pipenv by default hides the env and also creates noise with its lockfile.
@tecoholic Ah, I see what you mean
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!