Flush file after warning is written

Open
#85,223 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No source file or test is named in the issue. Start by reviewing the migrated BPO issue 41051 and PR #21000; done means the file is flushed after the warning is written.

Written by the indexing model from the issue text.

Description

3.13 topic-IO type-feature
BPO 41051
Nosy @manueljacob
PRs
  • python/cpython#21000
    		•

    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 2020-06-20.12:34:37.631>
labels = ['type-bug', 'expert-IO']
title = 'Flush file after warning is written'
updated_at = <Date 2020-09-27.00:06:07.034>
user = 'https://github.com/manueljacob'

    bugs.python.org fields:

    activity = <Date 2020-09-27.00:06:07.034>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2020-06-20.12:34:37.631>
creator = 'mjacob'
dependencies = []
files = []
hgrepos = []
issue_num = 41051
keywords = ['patch']
message_count = 1.0
messages = ['371934']
nosy_count = 1.0
nosy_names = ['mjacob']
pr_nums = ['21000']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41051'
versions = []

    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.