etree.Resolver.resolve_*() base_url doesn't work
Bug #1568167 reported by
Michael van Tellingen
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxml |
New
|
Undecided
|
Unassigned |
Bug Description
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
To post a comment you must log in.
Updated test-case which doesn't rate-limit