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

Ouverte
#56,086 52 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
30/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Calme
Stack technique
python
Domaine
operating-systems

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

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']

    Langage dominant
    Python
    Étoiles
    77.2k
    Forks
    36k
    Merge moyen
    1 j 9 h
    PR mergées (30 j)
    558

    Guide de contribution

    Ouvrir le guide de contribution

    Par où commencer

    1. Lisez l'issue en entier, puis le guide de contribution du projet.
    2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
    3. Forkez le dépôt et travaillez sur une branche.
    4. Ouvrez une pull request qui référence le numéro de l'issue.

    Autres issues de python/cpython

    Toutes les issues de python/cpython

    Issues similaires

    Plus d'issues Python

    Recevez les nouvelles issues par e-mail

    Un résumé court des issues GitHub adaptées aux débutants.