test: show we can use namedtuples and web3 namedtuples #2171
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What I did
** Unable to have underscore prefixed values in structs which is bad / breaking for Ape... I get it is rare but it is rather unfortunate. I don't see a reason to change our Struct to use namedtuple for reasons like this, also because the name in the namedtuple is not very dynamic in web3.py, it is the same name and not the name of the struct like it is in Ape. Ape's struct seems a lot more powerful so I am tempted to stick with that, albeit overengineered in some respects. I just can't rationalize changing to namedtuple at this time.
fixes: #1893
Checklist