![](https://secure.gravatar.com/avatar/05d3bb173713abb68ffaa1e2041bb6a9.jpg?s=120&d=mm&r=g)
Am 13.01.2017 um 16:25 schrieb Jim Fulton:
On Fri, Jan 13, 2017 at 7:23 AM, Thomas Güttler <guettliml@thomas-guettler.de <mailto:guettliml@thomas-guettler.de>> wrote:
What is an application for you?
Another way to think about this, FWIW, is to distinguish between the "whole system" (for which "Application" is often a useful shorthand), as opposed to components (aka libraries).
It's important for components to be flexible, so they're typically very flexible about versions of their dependencies.
For whole systems, OTOH, it's important that once a configuration is tested, that the same configuration is used in production, so systems typically pin all of their dependencies, ideally extending to their environments (which is a reason why container technology is attractive).
Yes, install_requires in setup.py should define flexible dependencies, but requirements.txt should define fixed dependencies via fixed version. Do you agree with my sentence from above? -- Thomas Guettler http://www.thomas-guettler.de/