search

mattmakai / fullstackpython.com

Full Stack Python source with Pelican, Bootstrap and Markdown.
https://www.fullstackpython.com/
MIT License
2.88k stars 627 forks source link

Library vs Application #127

Open guettli opened 7 years ago

guettli commented 7 years ago

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?

mattmakai commented 7 years ago

Hi @guettli, I agree with you the page can be dramatically improved. I think it was written 3-4 years ago and there's been some changes in handling app dependencies for Python and my explanation can be made much better.

If I've understood your comment correctly, I'm not sure I agree with the requirements.txt being only an output of the build process. A requirements.txt file is standard for installing dependencies, especially pegged dependencies, when you're building applications. setup.py is typically used within libraries you are distributing.