wsgiref.util FileWrapper raises ValueError: I/O operation on closed file.

Open
#70,487 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
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start with the attached wsgitest.py, which demonstrates the failure, and inspect the wsgiref.util.FileWrapper entry point. Reproduce the ValueError involving a closed file, then determine the expected behavior and add coverage for it. Done means the demonstrated case no longer raises unexpectedly and the relevant regression test passes.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 26299
Nosy @pjeby
Files
  • wsgitest.py: demonstrates the issue
    		•

    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 2016-02-05.18:40:05.816>
labels = ['library']
title = 'wsgiref.util FileWrapper raises ValueError: I/O operation on closed file.'
updated_at = <Date 2016-02-07.11:21:48.517>
user = 'https://bugs.python.org/samwyse'

    bugs.python.org fields:

    activity = <Date 2016-02-07.11:21:48.517>
actor = 'SilentGhost'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-02-05.18:40:05.816>
creator = 'samwyse'
dependencies = []
files = ['41828']
hgrepos = []
issue_num = 26299
keywords = []
message_count = 1.0
messages = ['259685']
nosy_count = 2.0
nosy_names = ['pje', 'samwyse']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue26299'
versions = ['Python 2.7', 'Python 3.6']

    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.