|
doesn't change the fact that this is a bad practice, there are tons of products successfully managing requirements.txt with min or max versions,
if the problem is dependency collision, then Caliber should have been the one to include and reference all the external libraries it needs (and not the plugins or users), and it should have load the user plugins in a separate runtime, allowing each plugin to run based on the requirements it needs (without the user having to deal with it or take care of it),
but as i said before ... i guess i am not the first to notice these cavities and not here to change the product, just to understand how to make it work
|