Make ElementTree event handling more modular to allow custom targets for the non-blocking parser

Open
#63,102 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reviewing the ElementTree non-blocking parser implementation and the linked PRs gh-156888 and gh-157439, since no source files or tests are named. The work is done when event handling is modular enough to support custom targets for the non-blocking parser.

Written by the indexing model from the issue text.

Description

stdlib topic-XML type-feature
BPO 18902
Nosy @jcea, @scoder, @jkloth

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-09-02.00:03:41.532>
labels = ['type-feature', 'library']
title = 'Make ElementTree event handling more modular to allow custom targets for the non-blocking parser'
updated_at = <Date 2013-09-28.17:43:11.005>
user = 'https://bugs.python.org/elibendersky'

bugs.python.org fields:

activity = <Date 2013-09-28.17:43:11.005>
actor = 'scoder'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-09-02.00:03:41.532>
creator = 'eli.bendersky'
dependencies = []
files = []
hgrepos = []
issue_num = 18902
keywords = []
message_count = 8.0
messages = ['196758', '196830', '196832', '197552', '197590', '197606', '198526', '198537']
nosy_count = 4.0
nosy_names = ['jcea', 'scoder', 'jkloth', 'eli.bendersky']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue18902'
versions = ['Python 3.5']

Linked PRs
  • gh-156888
  • gh-157439
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.