Re: [lxml] Default parser with/without no_network

Hello all, An update: In testing the resolve_filename method when validating XML against the published standard's schematron, I found that a resolver using this method also has difficulties: a different ones to the default parser, but the same resource is implicated. The filename resolver seems to fail at the same point as a default resolver with no_network=True. Whether no_network is True or False does not seem to affect the behaviour of this resolve_filename resolver, however. I have update the Gist with two more tests using the filename resolver: https://gist.github.com/rogie-bas/e157501d12cff8ac0aafc0cc120ce8dc One other observation, it seems that this resolver is called twice for each resource lookup (cf., logging included with the Gist). Is that expected? I'm going to try getting a simple example written for this issue, to try to focus on what seems to work and what doesn't. Currently, on my list of suspects are: HTTP redirects and use of network; although neither of these completely fits as some resources appear to have been resolved despite being on the network or having been redirects. As always, any insights are appreciated. Roger ________________________________ This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system. ________________________________
participants (1)
-
Duthie, Roger J.A.