3 ms·
> I needed to pin 10 dependency versions manually to make it run um... You should have been pinning all your dependencies from the very start
by biorach 3y ago
> I needed to pin 10 dependency versions manually to make it run
um... You should have been pinning all your dependencies from the very start
- noitpmeder 3y agoAgreed, or if you dont, you should run pip-compile during CI/merge in order to pin every dependency in the entire tree. These are very solveable (and have been solved for a while) problems. It really pains me that most people are either unaware or do not dive deep enough below the surface to find them.
- YetAnotherNick 3y agoIt wasn't my code. I pin all my dependencies, but lot of python code has been written by people without software engineering experience like university students and to an extent ML engineers.
- biorach 3y agoOK but your occasional contention was that > Virtual environments doesn't solve any of the problems as python authors either don't specify the version or their dependency author doesn't specify it. This is a problem of lack of training or willful poor practice, not an issue with venvs themselves which absolutely do solve this issue. Agreed, the problem would not exist at all if an approach like that of say, node development, existed, but here we are.
- baq 3y agoBut only in what you deploy. For the love of God don’t pin versions in libraries unless you’re really sure it has a completely different api. That’s how you get a dependency graph with no solutions.