2 ms·
Pipenv was artificially elevated to its position of “popularity” by its maintainer who was able to use various connections to make it seem more official than it
by danpalmer 4y ago
Pipenv was artificially elevated to its position of “popularity” by its maintainer who was able to use various connections to make it seem more official than it was. I think this has done a lot of harm to Python packaging over the years. Packaging wasn’t in a great place, but the confusion, and Pipenv’s promises for newcomers really threw everything off course for a generation of new Python engineers.
- wirrbel 4y agoI think this is part of it, it did not help that during the process it got abandoned and that poetry filled the void. I liked pipenv from its user interface it just never got from the PoC stage to „polished“. The way forward would actually be to unify the dependency resolution mechanisms into a PIP implementation (iirc pip has drastically improved its dependency resolution in recent years) and converge the various projects.