A-shares fund-flow cannot use Tushare provider

[JoseWangEs]

In .env, user can set up tushare api key, but in fund_flow_tool.py, the functions won't use tushare as a provider. Actually, fund_flow_tool.py uses Eastmoney client as a only-one source, which always occur errors as follows: HTTPSConnectionPool(host='push2his.eastmoney.com', port=443): Max retries exceeded with url: /api/qt/stock/fflow/daykline/get?secid=1.603019&fields1=f1%2Cf2%2Cf3%2Cf7&fields2=f51%2Cf52%2Cf53%2Cf54%2Cf55%2Cf56%2Cf57%2Cf58%2Cf59%2Cf60%2Cf61%2Cf62%2Cf63%2Cf64%2Cf65&klt=101&lmt=0 (Caused by ProxyError('Unable to connect to proxy', RemoteDisconnected('Remote end closed connection without response'))). please fix the problem and make fund-flow using other providers.

[warren618]

Thanks for the report — dug into this.

fund_flow_tool.py (and its 3 siblings — dragon_tiger_tool.py, margin_trading_tool.py, northbound_tool.py) are single-source Eastmoney wrappers by design, not missing a fallback by accident — none of that data-tool family has a secondary provider today.

The ProxyError('Unable to connect to proxy', ...) in your trace, though, looks like it's coming from your own environment's HTTPS_PROXY setting rather than Eastmoney itself — the underlying requests calls pick up HTTP_PROXY/HTTPS_PROXY from your environment automatically, and that's the proxy refusing the connection, not Eastmoney. Worth checking whatever's setting HTTPS_PROXY in your environment and confirming that proxy is actually reachable — if you don't need one to reach Eastmoney, unsetting it should fix this immediately.

Adding a tushare (or other) fallback for real is a reasonable ask, but it's a product decision that touches all 4 single-source tools for consistency, not a quick patch to this one file — filed as #516 to track it properly.