-
-
Notifications
You must be signed in to change notification settings - Fork 7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential dependency conflicts between freqtrade and urllib3 #2077
Comments
Solution
@#1xmatthias Please let me know your choice. |
I think we pinned urllib3 due to a problem with requests (and probably forgot to unpin) I'll look into it - i suspect we can simply update urllib to the latest version, but i'll need to test a little |
I'm a kind of doubting... |
@hroff-1902 What are your doubts? |
That you are actually an AI... 😁 |
@hroff-1902 Sorry, I am not an AI, but I can become an AI in the future. ^_^ |
Thanks for the headsup, since requests has been upgrade we can safely update urllib3 now 👍 |
Hi, as shown in the following full dependency graph of freqtrade, freqtrade requires urllib3 (the latest version), while the installed version of requests(2.22.0) requires urllib3>=1.21.1,<1.26.
According to Pip's “first found wins” installation strategy, urllib3 1.25.3 is the actually installed version.
Although the first found package version urllib3 1.25.3 just satisfies the later dependency constraint (urllib3>=1.21.1,<1.26), it will lead to a build failure once developers release a newer version of urllib3.
Dependency tree--------
Thanks for your attention.
Best,
Neolith
The text was updated successfully, but these errors were encountered: