Provide a way for potentially long runtime difflib algorithms to be aborted by the caller (and report progress?)
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 25/100
Rechercherichtung
Start by reading the difflib SequenceMatcher ratio() and quick_ratio() entry points and review the linked difflib-diff.patch. Determine the caller-abort and progress-reporting API requirements, then add focused tests showing cancellation and progress behavior; done means the supported behavior is specified and verified.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
| BPO | 24904 |
|---|---|
| Nosy | @tim-one, @rhettinger, @gpshead, @rbtcollins, @jftuga |
| Files |
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 2015-08-20.22:18:07.911>
labels = ['type-feature', 'library']
title = 'Provide a way for potentially long runtime difflib algorithms to be aborted by the caller (and report progress?)'
updated_at = <Date 2022-02-07.13:36:55.864>
user = 'https://github.com/jftuga'
bugs.python.org fields:
activity = <Date 2022-02-07.13:36:55.864>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-08-20.22:18:07.911>
creator = 'jftuga'
dependencies = []
files = ['40217']
hgrepos = []
issue_num = 24904
keywords = ['patch']
message_count = 5.0
messages = ['248919', '248920', '248921', '248922', '412718']
nosy_count = 5.0
nosy_names = ['tim.peters', 'rhettinger', 'gregory.p.smith', 'rbcollins', 'jftuga']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue24904'
versions = ['Python 3.5']
- Vorherrschende Sprache
- Python
- Sterne
- 77.2k
- Forks
- 36k
- Ø Merge
- 1 T. 9 Std.
- Gemergte PRs (30 T.)
- 558
Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus python/cpython
-
docs pending
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
-
stdlib type-feature
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
-
stdlib type-feature
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
-
build type-bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
-
stdlib topic-email type-feature
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100