Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Remove strict versioning from requirements.txt
See original GitHub issueHi,
I noticed I’m unable to add this library to my project via pipenv due to ‘incompatible versions in the resolved dependencies’ pipenv error. This happens because some library vendors sticks to strict versions in their requirements.txt file like this:
requests==2.20.0
requests-oauthlib==1.0.0
Therefore if one library needs requests==2.20.0 while another library needs requests==2.12.4 then pipenv would be unable to satisfy those conditions.
Could we have a more relaxed versions specification, like the next example?
requests>=2.12.4
requests-oauthlib>=1.0.0
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sure we can do that. Let me check each one of the dependencies and what versions can we set as the minimum required.
Thanks!