2 ms·
One of the reasons I made pip-chill is to create an incentive to not bother with version numbers and just make your software always run against the latest versi
by rbanffy 2y ago
One of the reasons I made pip-chill is to create an incentive to not bother with version numbers and just make your software always run against the latest versions. If something breaks, fix it. If it's too hard to do it, maybe you depend on too many things. Leftpad feelings here.
Having your software depend on two different versions of a library is just asking for more pain.
BTW, I still need to fix it to run on 3.12+ in a neat way. For now, it runs, but I don't like it.
- theelous3 2y agoThis is a fun idea. I always do this currently with some non-core dependencies like black, linters, or dependencies I controll the versioning of. I can't imagine I'd use this on libraries that provide real functionality in prod code though. If you have an incident popping off and you find out your dependency resolution goblin has reared its little head at the same time, bad day ahead.
- rbanffy 2y agoYou can always replicate the precise configuration running on the server. I assume the software passed all tests before being deployed with those same exact versions.
- deleted 2y ago[deleted]