Remove ENS backward compatibility code in abi_ens_resolver (v7 TODO)

[abhinay]

What is the current behavior?

There is a try/except NameNotFound block in abi_ens_resolver that was marked with a TODO comment to remove it in Web3.py v7. Specifically:

try:
    return type_str, validate_name_has_address(_ens, val)
except NameNotFound as e:
    # TODO: This try/except is to keep backwards compatibility when we
    #  removed the mainnet requirement. Remove this in web3.py v7 and allow
    #  NameNotFound to raise.
    if not isinstance(_ens, StaticENS):
        raise InvalidAddress(f"{e}")
    raise e

This backward compatibility handling catches NameNotFound and converts it to InvalidAddress (unless _ens is a StaticENS). According to the comment, we intended to remove this logic once we no longer required backward compatibility for mainnet-only ENS.

---

What should happen?

• The try/except block should be removed so that NameNotFound is raised directly as intended in Web3.py v7.
• Code paths that depend on this legacy behavior should be updated or removed, and associated tests should be adjusted accordingly.

---

Additional context

• I’ve already prepared a PR that removes this code. This Issue is just to track the change and generate an Issue number for cross-referencing.
• If maintainers have feedback on timing (e.g., if it should wait for the next major release), we can discuss in this thread.

[abhinay]

#3581

[kclowes]

Thanks for this PR! Since v7 is stable, we'll have to hold onto this until v8. Added to v8 issue (#3539).

[abhinay]

Thanks for this PR! Since v7 is stable, we'll have to hold onto this until v8. Added to v8 issue (#3539).

Should I keep the PR open as-is or close it for now and reopen when you’re ready to start merging for v8?

[kclowes]

You can keep it open. We'll rebase and merge once we start work on v8. Thanks!