-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot set multiple providers #1701
Comments
Sorry for the confusion. We removed the functionality to set multiple providers on one web3 instance. IIRC it was because there was no logic to be able to cycle through providers so it didn't really seem to make sense to allow multiple providers. Apparently the docs didn't get updated though, sorry about that. One workaround is to have two different web3 instances, each with a different provider though if you want. I'll leave this open to make the doc change. |
Apologies for necro-bumping this issue, but there's still an inconsistency in the docs that sent me on a 2-hour long goose-chase until I eventually found this ticket. https://web3py.readthedocs.io/en/stable/ens_overview.html Step 2 under Setup says: "or list" gave me the impression I could specify multiple providers as a redundancy kinda solution in case one provider was down. I see now I will have to do that checking myself, but if that line could updated it would save some future confusion. |
Thanks for the note, @sk33z3r , and for introducing the term "necro-bumping" to my vocabulary. Fix incoming. |
pip freeze
outputwtr: https://web3py.readthedocs.io/en/stable/web3.main.html#providers
Control:
The text was updated successfully, but these errors were encountered: