requirments.txt dependencies do not match setup.py
See original GitHub issueThe requirments.txt
dependencies do not match the setup.py
dependencies. For example,
requirements.txt | setup.py | package |
---|---|---|
1.11.0 | 1.10.0 | six |
2018.1.18 | 2017.7.27.1 | certifi |
2.18.4 | 2.11.1 | requests |
This is causing issues for me since the versions in the setup.py
are very old. Moreover, setup.py
specifies strict dependencies instead of lower bounds.
Questions:
- Is there a reason for the inconsistency between
requirments.txt
andsetup.py
? - The
requirements.txt
does not appear to be used bysetup.py
– what is the purpose of having it in the repo? - Could we change the dependencies to be lower bounds to enhance the compatibility as packages are updated?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Reference requirements.txt for the install_requires kwarg in ...
In short, requirements.txt is not a setup.py alternative, but a deployment complement. Keep an appropriate abstraction of package dependencies in setup.py .
Read more >requirements.txt vs setup.py in Python - Towards Data Science
Discussing about the difference and use of requirements.txt, setup.py and setup.cfg files and how to handle package dependencies properly in Python.
Read more >[BUG] 61.0.0 breaks "setup.py install" by missing ... - GitHub
The issue is that the "setup.py install" command successfully installs the pywbem package, but upon import it turns out that dependent packages ...
Read more >install_requires vs requirements files
install_requires is a setuptools setup.py keyword that should be used to specify what a project minimally needs to run correctly. When the project...
Read more >User Guide - pip documentation v22.3.1
If SomeDependency is a sub-dependency, then add the new line. It's important to be clear that pip determines package dependencies using install_requires ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Third idea: You can house everything in
setup.py
by creating another section fortests_require
and/orextras_require
(and you could makedev
one of the extras). This would mitigate the need to have the core dependencies listed twice (and thus eliminate risk of versions being out of sync since you could get rid of therequirements.txt
). Then to set up a dev environment, you would dopip install -e tuspy[dev]
orpip install -e tuspy[test]
. See further documentation here: http://setuptools.readthedocs.io/en/latest/setuptools.html#declaring-extras-optional-features-with-their-own-dependenciesLooks great!