[issue9371] pulldom doesn't provide END_DOCUMENT or COMMENT nodes.

Change by Cheryl Sabella : -- nosy: +scoder ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9371] pulldom doesn't provide END_DOCUMENT or COMMENT nodes.

Change by Jonathan Gossage : -- pull_requests: +9635 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9371] pulldom doesn't provide END_DOCUMENT or COMMENT nodes.

Florian Mladitsch florian.mladit...@googlemail.com added the comment: I found the bug for the end_document event and fixed it. But I couldn't figure out why the PullDOM class did not have comment-events. -- keywords: +patch nosy: +flomm Added file:

[issue9371] pulldom doesn't provide END_DOCUMENT or COMMENT nodes.

New submission from Mark Smith mark.sm...@practicalpoetry.co.uk: I've been developing unit tests to increase the code coverage for pulldom, and have discovered that comments and end_document do not appear to result in events being obtained from the DOMEventStream. I've attached a failing

[issue9371] pulldom doesn't provide END_DOCUMENT or COMMENT nodes.

Éric Araujo mer...@netwok.org added the comment: I tried looking at the doc to see if this was by design, and well, pulldom docs :) So I looked at the code, same thing, and finally read the commit history. It appears that pulldom is supposed to be DOM-compliant, so go ahead in adding unit