ElementTree.ParseError does not implement SyntaxError interface as expected

Open
#82,792 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api

Research direction

The payload names no files or tests. Start by locating ElementTree.ParseError and SyntaxError, then inspect the existing exception behavior and related tests. Done means the expected SyntaxError interface is clearly established and covered by a regression test, with the relevant tests passing.

Written by the indexing model from the issue text.

Description

3.8 (EOL) stdlib topic-XML
BPO 38611
Nosy @scoder, @jamercee

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 2019-10-28.09:11:14.949>
labels = ['3.8', 'library']
title = 'ElementTree.ParseError does not implement SyntaxError interface as expected'
updated_at = <Date 2019-10-30.02:12:26.485>
user = 'https://github.com/jamercee'

bugs.python.org fields:

activity = <Date 2019-10-30.02:12:26.485>
actor = 'xtreak'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-10-28.09:11:14.949>
creator = 'jamercee'
dependencies = []
files = []
hgrepos = []
issue_num = 38611
keywords = []
message_count = 2.0
messages = ['355518', '355686']
nosy_count = 2.0
nosy_names = ['scoder', 'jamercee']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue38611'
versions = ['Python 3.8']

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.