ruffsl added the comment:
> Included file paths should be collected only along an inclusion path and not
> across independent subtrees.
Yes, well put.
> Maybe we should add a "max_depth" parameter to limit the maximum recursion
> depth, defaulting to e.g. 5, that users
New submission from ruffsl :
I've been unable to login to bugs.python.org using Google's oauth.
After clicking the google oauth logo on the sidebar on bugs.python.org, I am
either slowly redirected to a google login page (after about 1 min) to select
an account, then after sel
ruffsl added the comment:
Hello @scoder,
Thanks for looking into this.
In addition to what I mentioned with lxml's use of the parent xml file's
respect dirname when attempting to open the include element's href, do you
think it would be possible to (optionally or by de
ruffsl added the comment:
I see it's been a few years, but I would still like to see
xml.etree.ElementInclude support nested xincludes, as lxml does. Additionally,
I'd like to have the default_loader attempt to open the href with respect to
the original xml file's dirname, as
