Contributors mailing list archives
Re: 14.0 branchesby
Acsone SA/NV, Denis Roussel
You can test the excellent pip deepfreeze https://pypi.org/project/pip-deepfreeze/ which includes a tool to see the dependencies tree of your project.
Indeed, it requires you install an environment with pip. But after few weeks of use, you won't want to use something else ;-)
Le ven. 9 oct. 2020 à 15:11, Daniel Reis <email@example.com> a écrit :
On 09/10/2020 11:32, Stéphane Bidoul wrote: > > @Simone, I think it's too early to say the other way is deprecated. > Let's give it some time. > Thank you for this work, The oca-dependencies.txt solution was a bit clumsy, and probably it is a good thing that is is being sunset. But I miss a way to get the equivalent information it gives me today. If I deploy from Git sources (I think most people do), the oca-dependencies.txt gives me good clues about what other OCA repos I should be also including in my project. I see some frustration coming, from not knowing what other repos we need to deploy to make the used modules work. Forcing people to still maintain oca-dependencies.txt is not a good solution. Since it is not used in tests it is not assured to be reliable, and it will still have the problem of being a repo-wide dependency, and possibly too much for the particular modules I'm interested in.. I would rather prefer to have a way to have the dependency repo information, based on particular modules. It would be perfect if I could run a command that would five me this information. If not possible, we should required the module README to state these dependencies, in the Install section. Thanks Daniel