3 ms·

Perhaps see this past discussion: https://news.ycombinator.com/item?id=18612590 https://news.ycombinator.com/item?id=18612590

• shantnutiwari 4y ago
  that doesnt explain anything -- pipenv was broken? So? Its an open source project, it will have issues now and then.
  • cpdean 4y ago
    For me the issue was less about the bugs in pipenv, and more about how Kenneth Reitz leveraged his commit rights to other projects' documentation to update them to claim that they all recommended pipenv when pipenv was in its infancy.
  • smcl 4y ago
    Sounds like it was a bit more than that, the top comment there looks quite damning: >However, Kenneth abused his position with PyPA (and quickly bumped a what is a beta product to version 18) to imply Pipenv was more stable, more supported and more official than it really was. > And worse still, for anyone saying "but ts open source, you get what you pay for", Kenneth as former Python Overlord at Heroku, encouraged Heroku to place Pipenv above Pip as the default Python package manager in the Python buildpack. This decision impacted paying customers and the Python buildpack used a broken version of Pipenv for a long time. So long, most people I know just went back to Pip. > Then, lastly, when people complained he had a tizzy at reddit and twitter and got PyPA to help backtrack and say "no we didn't support it, nope, its just a thing that happened", all while the main Pipenv Github repository was held under the PyPA GitHub Org.