You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has made the event of scraping an empty address, "aggressive" and forces downstream applications to catch a generic AssertionError, for this---in my case common---scenario. imho, getting an empty list back in case no records exist, is completely valid behavior?
Could you elaborate on why this behavior was chosen, and this change was made?
The text was updated successfully, but these errors were encountered:
in commit fb697e1 the following behavior was introduced:
to replace the UserWarning behavior:
This has made the event of scraping an empty address, "aggressive" and forces downstream applications to catch a generic
AssertionError
, 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?
The text was updated successfully, but these errors were encountered: