4 ms·
> this really turns into a headache fast as soon as you have ~4-5 in-house packages What’s a typical or better way of handling in-house packages?
by halfcat 2y ago
> this really turns into a headache fast as soon as you have ~4-5 in-house packages
What’s a typical or better way of handling in-house packages?
- belval 2y agoBy default pip will give you a warning that package X requires package Y ==1.0 but you have 1.1 which is incompatible instead of just failing. That's the feature that I'd like to have, basically a "--just-warn" flag or a way to set a package as "version does not matter". > What’s a typical or better way of handling in-house packages? Fixing your dependencies properly, but on some older codebases that pull also old dependencies this be a headache. For example "Pillow" a Python image library is a dependency in just about everything that manipulates images. This means that one package might have >=9.6<9.7, some package will have ==9.8 and another will have >=10<11. In practice it never matters and any of those version would work but you have a "version deadlock" and now you need to bump the version in packages that you may not actually own. Having some override of "this project uses Pillow==10, if some package ask for something else, ignore it" is something that pip does that uv doesn't.