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 摘要。