Skip to content

requirements versioning

A follow-up to opened discussion here by @tamas.gal : !86 (comment 180611)

Thinking about it now raises a more open question: Fixing a precise version in the requirements (in setup.py) is really a good thing?

  • it can become a drawback when integrating the library in a larger environment that would require, say requests==2.25 while we request requests==2.26 - though the library would perfectly work with requests v2.25.
  • is it really an improvement for reproducibility? The reproducible environment should come from the docker container, no? And in this case, the container does contain a fixed environment with fixed versions.

Or did I miss the meaning of your comment @tamas.gal?