Identify Moved Lines with difflib

Open
#67,979 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

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.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 23791
Nosy @terryjreedy
Files
  • python_diff_move.zip: Basic tests to impliment difflib move feature
    		•

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

    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.