ValueRaider

> seems like the "localize" call might be the culprit. > 'datetime.timezone' object has no attribute 'localize' Provide the traceback, so know which call you mean. Also, when this exception...

I think fix is this: replace this line: https://github.com/ranaroussi/yfinance/blob/1edeaf07dc8ea9129e37f08dc770c1e3a16f431f/yfinance/base.py#L654 with this: ``` dt_now = pd.Timestamp.utcnow() ``` Try that and report back

> I have the duplicated error “No timezone found, symbol may be delisted”. how to solve it? No idea. [You have to debug](https://github.com/ranaroussi/yfinance/issues/1268#issuecomment-1464898946)

@TapeReaderJoe Can you submit a Pull Request? #1084

@KevinYew97 I've edited that post with a working link

Basically `history` and `download` are fast, everything else is slower - `info` is the worst at 6.5x slower. Also you can quickly call `history` 100s-1000s times in a loop before...

The number of calls is less important than the amount of work those calls triggers at Yahoo. For whatever reason, `info` is ~6.5x more costly to Yahoo than `history`. Another...

90% of the time spent fetching & constructing `info` in `yfinance`, is spent only on the web request itself. There is only one web request. All of the decrypting and...

You're missing that most users won't need `info` anymore, because they only want market cap, or last price, or currency, which can be provided without `info` faster.

~Yes~ No Delete those specific keys from `info`, deliberately breaking users' code so they switch. But also provide clear documentation, and probably a message when importing `yfinance`, so transition is...