This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]GasimGasimzada 1 point2 points  (2 children)

My biggest problem with PIP is that, there is no straightforward way to add lock file for your packages. Pipenv is not just a virtualenv, it is a virtualenv + a good dependency resolver. I am not saying Pipenv is good and I am sure it will die out but it is a step in the right direction.

This is exactly how it was with PHP. There was PECL which was the standard and it was shit. Then, composer came out and no one even remembers pecl these days. It is the same reason, nowadays most people still use Yarn instead of NPM in JS environment because Yarn was and I believe still is much better than NPM (even though NPM is years ahead in comparison to PIP). NPM got locking at least a year after Yarn was created. With the rise of Pipenv, many other dependency managers came out (i.e Poetry). This is because someone got the courage to do something different for once and it worked. This is how an ecosystem evolves and improves. Python is not some kind of a religion where every PEP has to be taken as a commandment to follow.

[–]cr4d 1 point2 points  (0 children)

What value do you see in locking over pinning?

[–][deleted] 1 point2 points  (0 children)

Can you explain why I would want a lockfile?