Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
Aloha, Gitcoiners! How do you feel about Data Dignity, Quadratic Voting, Quadratic Finance and Decentralized Identity?
KERNEL is an 8-week, invite-only program for top tech talent looking to build relationships, products, and companies in blockchain and Web 3. 100 tal…
Type in [[ 2- term.length]] more characters to get results
[[ result.title ]]
[[ result.description | truncate(70) ]]
No matches found
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
* Version: 3.x and 4.x
### What was wrong?
In `3.x` if no ABI is provided when instantiating a contract instance you would get an unhelpful error message as seen here: https://github.com/ethereum/web3.py/issues/696
In `4.x` this type of error won't occur, however, the situation can still be approved because the `contract.functions` API simply won't have any accessible functions.
### How can it be fixed?
I don't think we need to fix `3.x` but we *could* provide a simple patch to raise a better error message if `self.abi` is `None`.
In `4.x` I think that we can improve the situation. Maybe accessing `contract.functions` when `abi is None` should raise an exception that no contract ABI was provided (same for accessing `contract.events`).