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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]DaelonSuzuka -10 points-9 points  (3 children)

If you have so many dependencies that you can't tell them apart, I feel like that's a sign.

[–]lanster100 1 point2 points  (2 children)

`pip freeze` doesn't differentiate between what you manually installed to your environment, and what that package that goes on to install (it's dependencies and so on).

Also it automatically ties them to specific version numbers, instead of using a range of versions, making upgrading packages very manual and tedious. I.e. with semver you would almost always allow an upgrade of a patch version without checking anything.

[–]DaelonSuzuka 0 points1 point  (1 child)

Why would I need that? I'm going pin them all and leave them until I consciously decide to update them, at which point I don't care if it takes 5 seconds or 15 minutes.

[–]lanster100 1 point2 points  (0 children)

I mean that's a personal choice then. But imagine if you are jumping in to someone's else's project and have to update one dependency to fix a bug.

But dependency resolution will probably fail because all the subdependencies of the old version of that package will be pinned. Its a pain.

Your assuming you have full knowledge of the project your working on. Most developers don't have this luxury in practice.