Skip to content
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

Autoconfigured web3 #302

Closed
carver opened this issue Sep 14, 2017 · 8 comments
Closed

Autoconfigured web3 #302

carver opened this issue Sep 14, 2017 · 8 comments

Comments

@carver
Copy link
Collaborator

carver commented Sep 14, 2017

What 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
@carver carver changed the title Want an autoconfigured web3 Autoconfigured web3 Sep 14, 2017
@gitcoinbot
Copy link

gitcoinbot commented Oct 2, 2017

This issue now has a funding of 0.01 ETH (3.02 USDT) attached to it. To view or claim this funding, click here.

@pipermerriam
Copy link
Member

pipermerriam commented Oct 2, 2017

@gitcoinbot 🏩 this is gonna be interesting.

@sbc64 sbc64 mentioned this issue Oct 10, 2017
@pipermerriam
Copy link
Member

@Sebohe just in case you didn't notice, once you've got #344 done and merged there is a bounty you can collect: https://gitcoin.co/funding/details?url=https://github.com/pipermerriam/web3.py/issues/302

@jasonrhaas
Copy link
Contributor

It looks like this issue has been merged in already, so the issue can be closed out.

@carver carver closed this as completed Nov 29, 2017
@carver carver reopened this Nov 29, 2017
@carver
Copy link
Collaborator Author

carver commented Nov 29, 2017

@owocki I tried to "accept funding claim" and got:

No active funding found at this address. Are you sure this is an active funded issue?

I closed the issue first and tried it, then reopened and tried it. Both with the same result. Can you pay it out (or tell me how to do it correctly?).

@carver carver closed this as completed Nov 29, 2017
@owocki
Copy link

owocki commented Nov 29, 2017

@carver sorry. that error message is wrong. its erroring out because i submitted the bounty from one of my wallet accounts and only the submitter can accept the bounty. im accepting it now (and will update the error copy by EOW)

@owocki
Copy link

owocki commented Nov 29, 2017

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.

@gitcoinbot
Copy link

⚡️ A tip worth 0.05 ETH has been granted to @Sebohe for this issue. ⚡️

Nice work @Sebohe, check your email for further instructions. | Send a Tip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants