Library packages should not exactly pin dependencies
jayqi opened this issue · 0 comments
jayqi commented
The mapillary package is something that I would like to use as a library in my project, i.e., I install it as a dependency and import functionality from mapillary modules.
However, it currently looks like all of mapillary's dependencies are locked to exact versions.
Line 175 in 323290f
This makes it really challenging to install mapillary into a virtual environment with other packages that might share dependencies.
It's not a typical practice to pin/lock dependencies for libraries. It makes sense for applications, but libraries are meant to be used by downstream consumers and dependencies need to be resolvable alongside other packages.
Some examples of discussion on this topic: