> Somehow pipenv got endorsed as an official tool by PyPA far before it was ready for production. Pretty much nails it for me. Being up to date with new techno

> Somehow pipenv got endorsed as an official tool by PyPA far before it was ready for production. Pretty much nails it for me. Being up to date with new technologies and tools is important, and once it became officially endorsed I (and many others) had to run with it. It was about 3 months I tried it last time, but at that time it was still slow, it ignored ~/.pip/pip.conf and also had no "proxy" CLI option like pip does. I hope it have changed now but early on it also had some strange preference to environment variables rather than CLI options, which I find odd for an application aimed for command line. I voiced my concerns about these issues, because why not? If I as a developer release something and intend to continue maintain it, I have a responsibility towards the users that depend on my creation. Old-fashioned stance perhaps...