Concurrent.futures base concurrency improvement (with patch)

Ouverte
#64,715 10 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
À l'abandon
Stack technique
python
Domaine
backend

Piste de recherche

Read Lib/concurrent/futures/_base.py and the linked futures-base.patch and futures-base-v2.patch first. Determine the intended concurrency change and account for the quick-yield lock-release fix described in the second patch; done means the implementation matches that scope.

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

Description

stdlib topic-multiprocessing type-feature
BPO 20516
Nosy @brianquinlan, @pitrou, @vstinner, @PCManticore
Files
  • futures-base.patch: Patch for /Lib/concurrent/futures/_base.py
  • futures-base-v2.patch: Fixed bug: Quick yield did not release lock on future
    		•

    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-02-05.02:56:55.706>
labels = ['type-feature', 'library']
title = 'Concurrent.futures base concurrency improvement (with patch)'
updated_at = <Date 2014-10-04.18:21:07.979>
user = 'https://bugs.python.org/glangford'

    bugs.python.org fields:

    activity = <Date 2014-10-04.18:21:07.979>
actor = 'pitrou'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-02-05.02:56:55.706>
creator = 'glangford'
dependencies = []
files = ['33920', '33999']
hgrepos = []
issue_num = 20516
keywords = ['patch']
message_count = 10.0
messages = ['210286', '210579', '210618', '210621', '210630', '210640', '210659', '228469', '228470', '228471']
nosy_count = 5.0
nosy_names = ['bquinlan', 'pitrou', 'vstinner', 'neologix', 'Claudiu.Popa']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue20516'
versions = ['Python 3.5']

    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.