3 ms·
Pretty much all stuff that tools like pipenv do, is something that anyone proficient with pip can do on their own. Their "advantage" lies in standardizing, so p
by toyg 4y ago
Pretty much all stuff that tools like pipenv do, is something that anyone proficient with pip can do on their own. Their "advantage" lies in standardizing, so people don't have to find out if you called the lockfile "requirements.txt.lock", "requirement.lock", or something else.
Unfortunately they create another learning curve, another leaky abstraction layer, another point of failure, etc etc...
- nurettin 4y agoTo add to that, the suspicious steps are: manually adding root dependencies. What if you forget? Not locking. What if you forget? Locking invalid versions. What if you don't check all is compatible first? How do you handle dev requirements? requirements_dev? but then how do you lock? The good thing is: you got rid of dependency walking and slow locking. As with everything, there is a tradeoff that I was willing to take.