Many incremental codecs don’t handle fragmented data

Open
#64,331 12 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
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reading the linked BPO dependencies and the attached zlib-reader.patch and inc-codecs.diff, then compare how the affected incremental codecs process fragmented data. Done means the identified codec cases consistently handle fragmented input, with the issue’s patch-review concerns resolved.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 20132
Nosy @malemburg, @loewis, @doerwalter, @ncoghlan, @vstinner, @vadmium, @serhiy-storchaka
Dependencies
  • bpo-13881: Stream encoder for zlib_codec doesn't use the incremental encoder
  • bpo-16473: quopri module differences in quoted-printable text with whitespace
  • bpo-20121: quopri_codec newline handling
  • bpo-23231: Fix codecs.iterencode/decode() by allowing data parameter to be omitted
  • bpo-27799: Fix base64-codec and bz2-codec incremental decoders
    		•
    Files
  • zlib-reader.patch: zlib StreamReader + API clarification
  • inc-codecs.diff: Fix bytes-bytes except StreamReader
    		•

    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-01-05.13:48:58.421>
labels = ['type-bug', 'library']
title = 'Many incremental codecs don\xe2\x80\x99t handle fragmented data'
updated_at = <Date 2016-08-19.12:08:31.462>
user = 'https://github.com/vadmium'

    bugs.python.org fields:

    activity = <Date 2016-08-19.12:08:31.462>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-01-05.13:48:58.421>
creator = 'martin.panter'
dependencies = ['13881', '16473', '20121', '23231', '27799']
files = ['37718', '37846']
hgrepos = []
issue_num = 20132
keywords = ['patch']
message_count = 12.0
messages = ['207374', '207850', '207900', '226679', '232850', '234099', '234100', '234102', '234104', '234122', '234651', '273108']
nosy_count = 7.0
nosy_names = ['lemburg', 'loewis', 'doerwalter', 'ncoghlan', 'vstinner', 'martin.panter', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue20132'
versions = ['Python 3.4', 'Python 3.5']

    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.