Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Autoconfigured web3
See original GitHub issueWhat was wrong?
In code examples, and short scripts, it’s a real PITA to show the ramp-up needed to get web3 working. It conveys that things are going to be tedious (an unfair first impression, I hope):
from web3 import Web3, IPCProvider
w3 = Web3(IPCProvider())
How can it be fixed?
Instead, I would love to have an autoconfigured web3, especially for some default cases, like localhost on 8545, and the geth IPC file.
from web3.auto import w3
This could try to connect to IPC in common locations and then localhost:8545
Or if you are running both IPC and HTTP, and want to give it a hint, that might look like:
from web3.auto.http import w3
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
also @Sebohe i just made an executive decision that you work here is worth more than 0.01 ETH ( we funded the bounty very early in the project, before the real funding came in), so i’m going to tip you more than the bounty amount to close this out.
This issue now has a funding of 0.01 ETH (3.02 USDT) attached to it. To view or claim this funding, click here.