You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My apologies to the workshop group. You unintentionally became documentation testers. The good news is that your struggles were not in vain! I marked down what I could about where people got stuck, and we'll see what we can do about improving the situation.
What was wrong?
Old version of pip, setuptools
Run virtualenv setup in python console
Virtualenv not installed
Using python 2, ended up with web3 v3, because there is no v4 version available
Using web3 v3 (missed "--pre" during install)
Connection/Provider is very confusing for people: why do they have to connect to anything? how do they specify what to connect to? what are all these different providers for and why are we making them pick one?
Tried to use web3.auto for infura
Can't deploy via infura
Faucet down
Ethtoken example only works on mainnet
Ethtoken docs did not show how to customize w3
People not clear when w3 is calling the node and when working locally
Didn't know how to fix address checksum error
Pip wasn't installed
Could not understand solc missing error (installed separate from pysolc)
How can it be fixed?
Add pip & setuptools update to quickstart instructions
Clearer distinction between shell and python interpreter
Add (link to) instructions for installing virtualenv
Use the new pip setup.py attribute python_requires to give a cleaner error message
Wait for v4 release
Deep dive on basic questions, like "Why do I need to connect to a node?"
Maybe link to new "choosing a node" docs in exception when web3.auto.w3 can't find the node?
In docs, link to a list of several faucets for different testnets. (There's probably already a good ESE post with this
Write a working ethtoken example for testnet
Add ethtoken docs for customizing w3 in ethtoken for testnet
In v5, consider a separate Web3.utils attribute that is clearly never hitting the network (can host things like: type conversions, sha3, eth-account) Planned v5 changes #722 (similar to web3.js v1 approach)
My apologies to the workshop group. You unintentionally became documentation testers. The good news is that your struggles were not in vain! I marked down what I could about where people got stuck, and we'll see what we can do about improving the situation.
What was wrong?
Provider
is very confusing for people: why do they have to connect to anything? how do they specify what to connect to? what are all these different providers for and why are we making them pick one?How can it be fixed?
Add pip & setuptools update to quickstart instructionsClearer distinction between shell and python interpreterAdd (link to) instructions for installingvirtualenv
Use the new pip setup.py attributepython_requires
to give a cleaner error messageWait for v4 releaseDeep dive on basic questions, like "Why do I need to connect to a node?"web3.auto.w3
can't find the node?Wait for Constructor Functions #666In docs, link to a list of several faucets for different testnets. (There's probably already a good ESE post with thisWeb3.utils
attribute that is clearly never hitting the network (can host things like: type conversions, sha3, eth-account) Planned v5 changes #722 (similar to web3.js v1 approach)Improve warning on failed address checksum #716 -> Improved error message on address validation #803Add (link to) pip install instructions for a variety of platformsThe text was updated successfully, but these errors were encountered: