I am unsure whether the current text gives new comers a clear and simple guide line.
https://www.fullstackpython.com/application-dependencies.html
Library vs Application
I think programming is done in libraries and application only contain configuration.
This means if you do programming, then you are inside a library. Even if the library is only used in one place up to now .... but maybe you are successful and you get new customers ...
That's why I think dependencies in Python are done via install_requires in setup.py.
For me requirements.txt is only the result of a successful continuous integration run, created by "pip freeze". This is a good working set since all tests were ok.
Please hit me with arguments and tell me what's wrong with my point of view.
Back to topic:
I think "Library vs Application" could be improved on this page: https://www.fullstackpython.com/application-dependencies.html
What do you think?
I am unsure whether the current text gives new comers a clear and simple guide line.
https://www.fullstackpython.com/application-dependencies.html
Library vs Application
I think programming is done in libraries and application only contain configuration.
This means if you do programming, then you are inside a library. Even if the library is only used in one place up to now .... but maybe you are successful and you get new customers ...
That's why I think dependencies in Python are done via install_requires in setup.py.
For me requirements.txt is only the result of a successful continuous integration run, created by "pip freeze". This is a good working set since all tests were ok.
Please hit me with arguments and tell me what's wrong with my point of view.
Back to topic:
I think "Library vs Application" could be improved on this page: https://www.fullstackpython.com/application-dependencies.html
What do you think?