Dependency management about platalea HOT 3 CLOSED

Let me add @gchrupala to the discussion as he might have some opinion on this.

from platalea.

My understanding is that for library code dependencies should be specified permissively in setup.py, while for code which reproduces a specific set of experiments/results we specify the exact versions of each dependency in requirements.txt. Currently platalea is both (which would mean using requirements.txt as the more strict option); I suppose we could separate it into library and experiment code.

from platalea.

Agreed, as discussed. For paper repos we'll use requirements.txt to specifically pin requirement versions and/or source repositories, for the general library we use setup.py as permissively as possible.

We could also call requirements.txt something different, for instance requirements_paper_[identifier].txt to make this more explicit.

For platalea, what does this mean? Should we make clear in the readme what paper(s) this requirements.txt corresponds to? Or should we remove it here and put it in a separate repo for that paper?

from platalea.