4 ms·

Thanks a lot, that's a great intro to many useful tools. I have 2 questions. Managing dependencies "If you’re developing a library, use nothing. Let your user

Thanks a lot, that's a great intro to many useful tools. I have 2 questions. Managing dependencies "If you’re developing a library, use nothing. Let your users decide, and give them as much flexibility as possible to maximize compatibility (don’t pin, unless to exclude some known-to-fail version ranges)." What does this "nothing" contain? :-) A `requirements.txt`? Do you test the library with various versions of that dependency (e.g. with tox)?

gcarvalho 4y ago
My bad! That part should have been clearer. I mean you don't need pinned dependencies. Just declare the dependencies as you would normally in install_requires (from setup.cfg) and that's it. No need for pinning exact dependency versions with pip-tools, therefore no requirements.txt. I think the standard practice is to just test the library against the latest version of its dependencies. In the case a new release of a dependency causes breakage, then you update your install_requires to restrict the version.