in commitfb697e1 the following behavior was introduced:

# etherscan/utils/parsing.pyassertstatus,f"{result} --{message}"

to replace the UserWarning behavior:

#etherscan/utils/parsing.pywarnings.warn(f"{result} --{message}")

This has made the event of scraping an empty address, "aggressive" and forces downstream applications to catch a genericAssertionError, for this---in my case common---scenario. imho, getting an emptylist back in case no records exist, is completely valid behavior?

Could you elaborate on why this behavior was chosen, and this change was made?