Catch 404 in paging next

[felix-hilden]

Fixes #145, this works but I don't like the solution. I'd like to refactor it in some way. See also this question on SE Code Review.

[felix-hilden]

We could at least simplify a bit: use a larger exception hierarchy to catch only 404 in the except.

[HarrySky]

I tried to use decorator for catching 404 error, but in the end this idea did not work, since somewhere should be two versions of this try-catch block - one with await keyword and one without.

Idea I got - modifying handle_errors function to remove body from response if 404. That way you will return None. But it is a bit hack-ish :)

Your solution is not that bad, maybe there is no way to reduce duplication in case of try-catch with both async and sync variants. But maybe SE code review question will provide one.

P.S. I forgot to say thank you for your library - I restored part of my Melodiam webservice with it and will continue adding/restoring more features 👍

[felix-hilden]

Thanks for trying it out anyway! Yeah, I wouldn't call removing the body an optimal solution. I think we'll go with expanding the exceptions.

You're most welcome! Your help with the async client was invaluable. I'm glad it enabled you to restore your application!