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

2019-05-30 Thread Cheryl Sabella
Change by Cheryl Sabella : -- nosy: +scoder ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

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

2018-11-05 Thread Jonathan Gossage
Change by Jonathan Gossage : -- pull_requests: +9635 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

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

2016-01-15 Thread Martin Panter
Changes by Martin Panter : -- stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

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

2012-03-11 Thread Florian Mladitsch
Florian Mladitsch 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: http://bugs.python.org/file24787/pulldom_enddoc_event_fix.patch _

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

2010-07-24 Thread Éric Araujo
Éric Araujo 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 tests for that and fi

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

2010-07-24 Thread Mark Smith
New submission from Mark Smith : 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 TestCase to demonstrate this. --