Unpin requirements.txt
See original GitHub issue
Top Results From Across the Web
Unpin packages in `requirements.txt` · Issue #312 - GitHub
We have a lot of packages in our requirements.txt file that are pinned to a specific version. As the Python packaging user guide...
Read more >Pin Your Packages - nvie.com
Typically, in Python apps, you include a requirements. txt file in the root of your project directory, and you run pip freeze >...
Read more >Should I pin dev requirements as well, or just the installation ...
I think the right answer here is that there should be two files, one with permissive requirements and one with a pinned, tested...
Read more >Our Comprehensive Guide to Python Dependencies - Kiwi.com
Detecting unpinned requirements. In your *requirements.txt file you should have all requirements pinned to specific versions. This guarantees that you have the ...
Read more >Pin All Dependencies (& Let Pip Sort 'Em Out) - Promptworks
Dependency pinning is explicitly specifying the exact version of a dependency. That means instead of your requirements.txt looking like this:
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
As we’re getting close to getting #246 merged, I wanted to leave a note of appreciation for @andersk for getting us out of this impasse. You both came up with multiple suggestions (after taking the time to understand my perspective), and then also followed through and did the implementation. Thank you - gitlint is better because of it!
And @sigmavirus24 of course, for perspective and expertise (always 😃 )
Thank you!
Unfortunately, the Python packaging system doesn’t support extras that loosen dependencies rather than tightening them, nor does it support default extras (pypa/setuptools#1139).
A possible workaround would be to rename the main package to (say)
gitlint-core
, and havegitlint
be an empty package that just requiresgitlint-core[trusted-deps]
. But I’m not sure if maintaining two packages rather than one would be an improvement from your perspective, even if one is empty?Alternatively, what do you think about simply adding a question to the GitHub issue template asking whether the user installed with
pip install gitlint[trusted-deps]
as documented, and/or asking for the output ofpip freeze
?