You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting financial data sometimes takes way too longThe source of issue lies in this line. The session.get (...)uses IPv6 which some times does not work, while IPv4 works. (also discussed in this answer)
Simple code that reproduces your problem
Executing this piece of code a couple of times(or requesting any other financial data) even without surpassing yahoo finance's API constraint, will cause the next calls to yahoo finance really slow.
The text was updated successfully, but these errors were encountered:
ahnazary
changed the title
Requests to yahoo finance take way too long to be responded, while sending the same request via postman is responded with no issues
Requests to yahoo finance take way too long to be responded via yfinance, while sending the same request via postman is responded with no issues
Mar 6, 2024
ahnazary
changed the title
Requests to yahoo finance take way too long to be responded via yfinance, while sending the same request via postman is responded with no issues
Requests to yahoo finance take way too long to be responded via yfinance, while sending the same request via postman is responded instantly
Mar 6, 2024
Describe bug
Getting financial data sometimes takes way too longThe source of issue lies in this line. The
session.get (...)
uses IPv6 which some times does not work, while IPv4 works. (also discussed in this answer)Simple code that reproduces your problem
Executing this piece of code a couple of times(or requesting any other financial data) even without surpassing yahoo finance's API constraint, will cause the next calls to yahoo finance really slow.
Debug log
No bug logs, just takes too long to response.
Bad data proof
No response
yfinance
versionyfinance==0.2.37
Python version
Python 3.11.4
Operating system
MacOS
The text was updated successfully, but these errors were encountered: