Lungiselela i-proxy yeklayenti le-API v2 ye-Tweepy
Ku-Client ye-Tweepy 4.14, buyekeza i-client.session ngaphambi kwezingcingo ze-API esikhundleni sokusebenzisa ipharamitha ye-proxy ye-klasi ye-API v1.1.
Client.session iyiseshini ye-Requests ebhalwe phansi ye-Tweepy 4.14 yethrafikhi ye-API v2:
import tweepy
client = tweepy.Client(bearer_token=bearer_token)
client.session.proxies.update({
'http': 'http://proxy.example:8080',
'https': 'http://proxy.example:8080',
})Yenza izingcingo ze-v2 ngale klayenti ngemuva kokusetha imephu. I-endpoint evela kuhlu lwe-proxy ye-HTTP inganikeza umzila we-HTTP womphakathi walezi zindinganiso ze-proxy. Ithokheni ye-bearer iziqinisekisa kumhlinzeki; noma iyiphi i-akhawunti ekucushweni kwe-proxy iziqinisekisa kumxhumanisi.
Uma isibonelo se-API(proxy=...) sihluleka nalesi sakhi, hlola iklasi: leyo pharamitha ingeyye-API ye-Tweepy v1.1. Ukucushwa kwesinye iseshini se-Requests esizimele nakho akukushintshi client.session.
Ukuhlanganiswa kwemvelo ye-Requests kuhlala kuvuliwe, ngakho okokufaka kwe-proxy nokudlula okuzuzwe njengefa kungathinta ukukhetha. Izinto zokuqinisekisa noma zokusakaza ezidalwe ngokuzimela zingasebenzisa olunye uxhumano; lesi silungiselelo sihlanganisa iseshini ye-v2 eshiwo, hhayi lezo zinto noma imithetho yokufinyelela ye-API yomhlinzeki.