Identify Moved Lines with difflib
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 25/100
Rechercherichtung
Start by reviewing the attached python_diff_move.zip, which contains basic tests for the proposed difflib move feature. Read the existing difflib implementation and the included tests to determine the expected moved-line behavior. Done means the feature is implemented in the library and the basic tests pass, with additional coverage for the agreed behavior.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
| BPO | 23791 |
|---|---|
| Nosy | @terryjreedy |
| 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-03-27.16:25:20.365>
labels = ['type-feature', 'library']
title = 'Identify Moved Lines with difflib'
updated_at = <Date 2015-04-03.20:16:31.950>
user = 'https://bugs.python.org/bkiefer'
bugs.python.org fields:
activity = <Date 2015-04-03.20:16:31.950>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-03-27.16:25:20.365>
creator = 'bkiefer'
dependencies = []
files = ['38747']
hgrepos = []
issue_num = 23791
keywords = []
message_count = 2.0
messages = ['239416', '239649']
nosy_count = 2.0
nosy_names = ['terry.reedy', 'bkiefer']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue23791'
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