I-polling inento yayo yesicelo ku-python-telegram-bot 22.8. Ngakho-ke ucingo olujwayelekile lwe-API oluphumelelayo akufakazi ukuthi i-getUpdates ithole indlela efanayo ye-proxy.

Kuhlelo lwe-polling, lungiselela zombili izindlela:

from telegram.ext import Application

proxy_url = 'http://proxy-user:[email protected]:8080'
application = (
    Application.builder()
    .token(bot_token)
    .proxy(proxy_url)
    .get_updates_proxy(proxy_url)
    .build()
)

I-proxy ilungiselela imisebenzi ejwayelekile ye-Bot API; i-get_updates_proxy ilungiselela i-polling. Qhubeka usebenzisa ama-handler akhona kanye nomjikelezo wempilo we-polling noma we-webhook eduze kwalokhu kwakhiwa kohlelo.

Izifakazelo ze-URL ziyizindawo zokubamba. Thola amanani angempela ngomshini wezifakazelo wokusatshalaliswa futhi yenza i-percent-encoding yezinhlamvu ezigciniwe ezingxenyeni ze-URL. Sebenzisa i-scheme yangempela yomxhumanisi: i-HTTPXRequest yamukela ama-URL e-proxy ye-HTTP futhi isekela i-SOCKS5 ngokuncika kwe-SOCKS okudingwa yiphakethe. Uhlu lwe-proxy ye-SOCKS5 luhlinzeka ngabazongenela emkhawulweni wokugcina walolo hlelo, hhayi izifakazelo ze-akhawunti ye-proxy.

Uma uhlelo luhlinzeka ngezinto ezenziwe ngokwezifiso nge-request noma nge-get_updates_request, lungiselela lezo zinto ngendlela efanayo esikhundleni salokho. Isilungiselelo se-proxy ku-builder kanye nento yesicelo enikezwe ngokwehlukana kuyizinto zokufaka ezihlukile zendlela efanele.

Izindlela zakudala ze-Updater ezisebenzisa i-request_kwargs ne-urllib3_proxy_kwargs ziqondise kwesinye isizukulwane.

Izihloko ezihlobene