pulldom doesn't provide END_DOCUMENT or COMMENT nodes.

未關閉
#53,617 3 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
30/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
python
領域
backend

研究方向

Start by reviewing the historical test_pulldom.py and pulldom_enddoc_event_fix.patch, then inspect PR 10328 and the current pulldom implementation. Done means pulldom exposes END_DOCUMENT and COMMENT nodes with tests covering both behaviors.

由索引模型根據 Issue 內容生成。

描述

topic-XML type-bug
BPO 9371
Nosy @scoder, @merwok
PRs
  • python/cpython#10328
    		•
    Files
  • test_pulldom.py: A TestCase to demonstrate this issue.
  • pulldom_enddoc_event_fix.patch: bugfix for ENDDOCUMENT event
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
closed_at = None
created_at = <Date 2010-07-24.13:01:50.678>
labels = ['expert-XML', 'type-bug']
title = "pulldom doesn't provide END_DOCUMENT or COMMENT nodes."
updated_at = <Date 2019-05-30.20:00:25.245>
user = 'https://bugs.python.org/marksmith'

    bugs.python.org fields:

    activity = <Date 2019-05-30.20:00:25.245>
actor = 'cheryl.sabella'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['XML']
creation = <Date 2010-07-24.13:01:50.678>
creator = 'mark.smith'
dependencies = []
files = ['18183', '24787']
hgrepos = []
issue_num = 9371
keywords = ['patch']
message_count = 3.0
messages = ['111474', '111486', '155409']
nosy_count = 4.0
nosy_names = ['scoder', 'eric.araujo', 'mark.smith', 'flomm']
pr_nums = ['10328']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue9371'
versions = ['Python 3.2']

    主要語言
    Python
    星號
    77.2k
    分支
    36k
    平均合併
    1 天 9 小時
    30 天內合併 PR
    558

    貢獻指南

    開啟貢獻指南

    從這裡開始

    1. 先讀完整個 Issue，再讀專案的貢獻指南。
    2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
    3. Fork 儲存庫，在一個分支上完成修改。
    4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

    python/cpython 的其他 Issue

    查看 python/cpython 的全部 Issue

    相似的 Issue

    更多 Python Issue

    把新 issue 寄到你的電子郵件信箱

    精選適合新手參與的 GitHub issue 摘要。