Plistlib fails on certain valid plist values

Open
#67,182 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by inspecting Python's plistlib library and reproducing the failure with valid plist values; the issue does not identify the affected values, files, or tests. Done means plistlib handles the reproduced valid values correctly, with coverage for those cases.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 22993
Nosy @ronaldoussoren, @abalkin, @ned-deily, @serhiy-storchaka

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 2014-12-04.06:34:34.762>
labels = ['type-bug', 'library']
title = 'Plistlib fails on certain valid plist values'
updated_at = <Date 2016-04-08.12:08:39.917>
user = 'https://bugs.python.org/ConnorWolf'

bugs.python.org fields:

activity = <Date 2016-04-08.12:08:39.917>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-12-04.06:34:34.762>
creator = 'Connor.Wolf'
dependencies = []
files = []
hgrepos = []
issue_num = 22993
keywords = []
message_count = 6.0
messages = ['232107', '232108', '232110', '232112', '232115', '263024']
nosy_count = 5.0
nosy_names = ['ronaldoussoren', 'belopolsky', 'ned.deily', 'serhiy.storchaka', 'Connor.Wolf']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue22993'
versions = ['Python 2.7', '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.