Closed LefterisJP closed 1 year ago
I like this idea but we'll have to think about how to parse the error response to accommodate the most users. I can't remember if error code numbers are standardized across clients. I'll add this to our v6 breaking changes issue to discuss with the team. Eventually in v6 we're also planning on adding a Web3Exception
class that all of our custom exceptions will inherit from which should make things nicer too.
Eventually in v6 we're also planning on adding a Web3Exception class that all of our custom exceptions will inherit from which should make things nicer too.
Understood! That would be a really cool change.
Will be looking at the issue to see how it progresses :heart:
pip freeze
outputWhat was wrong?
Please include any of the following that are applicable:
Make this call via web3.py
https://nodes.mewapi.io/rpc/eth
How can it be fixed?
I think it would be much better if we, the users of web3, have a different exception to catch when a method is not available in the node, rather than raising a generic
ValueError
.How about
MethodUnavailable
?