Change os.fsync() to support physical backing store syncs

Open
#56,086 52 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
operating-systems

Research direction

Start by reviewing the linked 11877.9.diff, 11877-standalone.1.diff, and 11877.fullsync-1.diff files, then read the 51-message discussion at the original issue. Determine the intended physical backing-store sync semantics and platform scope before identifying the current os.fsync() implementation and its tests. Done means the behavior and supported platforms are agreed and covered by tests.

Written by the indexing model from the issue text.

Description

stdlib
BPO 11877
Nosy @ronaldoussoren, @pitrou, @vstinner
Files
  • 11877.9.diff
  • 11877-standalone.1.diff
  • 11877.fullsync-1.diff
    		•

    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 2011-04-19.11:35:37.946>
labels = ['library']
title = 'Change os.fsync() to support physical backing store syncs'
updated_at = <Date 2013-05-16.00:04:55.785>
user = 'https://bugs.python.org/sdaoden'

    bugs.python.org fields:

    activity = <Date 2013-05-16.00:04:55.785>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2011-04-19.11:35:37.946>
creator = 'sdaoden'
dependencies = []
files = ['22016', '22046', '22759']
hgrepos = []
issue_num = 11877
keywords = ['patch']
message_count = 51.0
messages = ['134043', '134063', '134071', '134084', '134142', '134143', '134144', '134145', '134147', '134148', '134151', '134154', '134179', '134213', '134214', '134215', '134221', '134236', '134252', '134253', '134379', '135453', '135457', '135458', '135462', '135520', '135573', '135655', '135699', '135803', '135824', '135847', '135862', '135865', '135870', '136037', '136048', '136158', '136175', '136177', '136180', '136214', '136219', '136431', '136432', '140608', '140657', '140920', '140982', '141121', '189331']
nosy_count = 7.0
nosy_names = ['ronaldoussoren', 'pitrou', 'vstinner', 'nadeem.vawda', 'neologix', 'santoso.wijaya', 'sdaoden']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue11877'
versions = ['Python 3.3']

    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.