El 28/04/2014 13:52, "Cédric Krier" <cedric.kr...@b2ck.com> va escriure: > > On 28 Apr 13:32, Raimon Esteve wrote: > > 2014-04-28 9:45 GMT+02:00 Cédric Krier <cedric.kr...@b2ck.com>: > > > On 28 Apr 09:19, Guillem Barba Domingo wrote: > > >> Hi, > > >> I think it would be useful to have Python library dependencies info in > > >> tryton.cfg > > >> I'm thinking in cases like "stdnum" in party module (it should be "extra > > >> depends") and "retrofix" in account_bank_statement module (it is third > > >> party module, but it's only an example of hard dependency). > > >> > > >> I'm thinking to have a notation like requirements.txt > > >> A fake example: > > >> version=3.2.0 > > >> depends: > > >> ir > > >> res > > >> extra_depends: > > >> xxx > > >> xml: > > >> yyy.xml > > >> python_depends: > > >> retrofix==0.3 > > >> python_extra_depends: > > >> stdnum>=1.0 > > >> > > >> The setup.py could use it to generate it's own dependencies, like it does > > >> with modules. > > >> The gain is that these info is more accessible if you don't install modules > > >> as packages. For example, it will be very useful to generate a > > >> requirements.txt for all module dependencies. > > >> > > >> what do you think? > > > > > > Useless. > > > > Usefull to generate values in setup file, similar get version module in setup. > > What's the point to generate a value that is used only in one place. > So it is definitly useless.
It allows to use this informatinformation in other places, like a little tool to generate a requirements.txt with all modules dependences. An alternative is add a requirements.txt (or requirements.in to be used with pip-tools), but with this solution you loss the information of strong vs extra dependencies, and the information wolud be duplicated.
