Generator-based HTMLParser

Open
#61,612 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reviewing the linked BPO issue 17410 and the attached htmltokenizer.patch, which is the only named implementation artifact. Read the existing HTMLParser implementation and its tests to determine the intended generator API; done means the generator-based behavior is implemented and the relevant tests pass.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 17410
Nosy @ncoghlan, @scoder, @ezio-melotti, @bitdancer, @karlcow, @flying-sheep
Files
  • htmltokenizer.patch: version 1.0.0.1 of the patch. tests still pass.
  • 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 2013-03-13.18:09:52.019>
    labels = ['type-feature', 'library']
    title = 'Generator-based HTMLParser'
    updated_at = <Date 2013-08-26.04:52:06.599>
    user = 'https://github.com/flying-sheep'
    

    bugs.python.org fields:

    activity = <Date 2013-08-26.04:52:06.599>
    actor = 'ncoghlan'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2013-03-13.18:09:52.019>
    creator = 'flying sheep'
    dependencies = []
    files = ['29402']
    hgrepos = []
    issue_num = 17410
    keywords = ['patch']
    message_count = 10.0
    messages = ['184096', '184100', '184101', '184103', '184104', '184105', '184106', '184107', '184108', '196179']
    nosy_count = 6.0
    nosy_names = ['ncoghlan', 'scoder', 'ezio.melotti', 'r.david.murray', 'karlcow', 'flying sheep']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue17410'
    versions = ['Python 3.4']
    

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.