HTTPError No Longer Thrown

[wmorgansoftware]

I am presently using a list of symbols where the designation is different between sources (i.e. Yahoo vs. broker); mostly geared around preferred stock. To compensate for this, I created on my end a symbol vs. alternates translation, and if YFinance was throwing a HTTPError from curl_cffi when trying to access Tickers.tickers[value].info , I would skip and move to the next in the list, later doing a translation comparison for the Yahoo version of the symbol to ensure I have the correct data.

However, after downloading a recent update (0.2.62), I noticed in my log "HTTP Error 404:" followed by a "successful" receipt of .info only containing the following dict:

{'trailingPegRatio': None}

If you've made a change to remove the throwing of this error, how am I to know that the find did error out? The last known "working" version was 0.2.59 .

[ValueRaider]

Did that ever actually raise before into your code? yfinance always tried to intercept errors internally and return None for invalid tickers.

#2524 will change this.

[ValueRaider]

The only relevant code changes I can find are adding _fetch_additional_info then fixing it:

• Add pre- / post-stock prices (and other useful information) #2212
• Fixes issue 2343 _fetch_info IndexError: list index out of range #2354
• Fix info IndexError #2382

[wmorgansoftware]

Clearly it did raise, otherwise I wouldn't have been able to use it beforehand, nor would I have reported that it raised in a previous version. But here's the code snippet I was using, seeing how your first reaction is to accuse me of lying:

from curl_cffi.requests.exceptions import HTTPError
...
  for quote in raw_data.tickers.values():

    print(quote)

    try:

      info = quote.info

    except HTTPError:

      continue

    print(info['symbol'])

[jfthuong]

seeing how your first reaction is to accuse me of lying

@wmorgansoftware , FYI nobody accused you of anything: they were just wondering that an error might have been raised before.