etree.Resolver.resolve_*() base_url doesn't work
Bug #1568167 reported by Michael van Tellingen on 2016-04-08
This bug affects 1 person
I'm having some issues with custom Resolvers. The base_url kwarg in resolve_*() methods don't seem to work.
See the attached testcase. Disabling the custom resolver fixes the issue