Order of _io objects finalization can lose data in reference cycles

Open
#67,185 6 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 gcio.py and gcgzipio.py examples, then inspect the relevant _io finalization behavior for reference cycles. Reproduce the reported data loss and establish the expected finalization order before determining what regression coverage is needed; done means cyclic _io objects no longer lose buffered data.

Written by the indexing model from the issue text.

Description

3.10 3.11 3.9 (EOL) interpreter-core topic-IO type-bug
BPO 22996
Nosy @pitrou, @vstinner, @serhiy-storchaka, @MojoVampire, @iritkatriel
Files
  • gcio.py
  • gcgzipio.py
    		•

    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.13:50:26.895>
labels = ['3.10', 'type-bug', '3.9', 'expert-IO', '3.11']
title = 'Order of _io objects finalization can lose data in reference cycles'
updated_at = <Date 2021-11-27.15:03:59.912>
user = 'https://github.com/pitrou'

    bugs.python.org fields:

    activity = <Date 2021-11-27.15:03:59.912>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2014-12-04.13:50:26.895>
creator = 'pitrou'
dependencies = []
files = ['37358', '37371']
hgrepos = []
issue_num = 22996
keywords = []
message_count = 6.0
messages = ['232138', '232161', '232162', '232179', '232180', '407149']
nosy_count = 5.0
nosy_names = ['pitrou', 'vstinner', 'serhiy.storchaka', 'josh.r', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue22996'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

    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.