Adapt bash readline operate-and-get-next function

Open
#66,424 17 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
bash, python
Domain
cli

Research direction

Review the linked readline.patch and the original BPO issue 22228 first. Determine the expected adaptation of bash's readline operate-and-get-next function, then verify that the behavior is implemented in CPython's extension-module area.

Written by the indexing model from the issue text.

Description

3.8 (EOL) extension-modules type-feature
BPO 22228
Nosy @Yhg1s, @stevendaprano, @Rosuav, @berkerpeksag, @vadmium, @lelit
Files
  • readline.patch
    		•

    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-08-19.09:42:08.257>
labels = ['extension-modules', 'type-feature', '3.8']
title = 'Adapt bash readline operate-and-get-next function'
updated_at = <Date 2020-12-20.13:15:35.652>
user = 'https://github.com/lelit'

    bugs.python.org fields:

    activity = <Date 2020-12-20.13:15:35.652>
actor = 'lelit'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2014-08-19.09:42:08.257>
creator = 'lelit'
dependencies = []
files = ['36414']
hgrepos = []
issue_num = 22228
keywords = ['patch']
message_count = 17.0
messages = ['225523', '225573', '252768', '252794', '268657', '268659', '268661', '268665', '268794', '269044', '269049', '269096', '335003', '335006', '335080', '383222', '383430']
nosy_count = 6.0
nosy_names = ['twouters', 'steven.daprano', 'Rosuav', 'berker.peksag', 'martin.panter', 'lelit']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue22228'
versions = ['Python 3.8']

    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.