Idle extension configuration and key bindings

Open
#66,895 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
desktop, tooling

Research direction

Start by reviewing the attached issue22706_1.diff and the IDLE-related entry points it changes. Check the historical issue discussion and existing tests before determining the intended configuration and key-binding behavior; done means the agreed feature is implemented and covered by appropriate tests.

Written by the indexing model from the issue text.

Description

topic-IDLE type-feature
BPO 22706
Nosy @terryjreedy
Files
  • issue22706_1.diff
    		•

    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-10-23.00:17:33.672>
labels = ['expert-IDLE', 'type-feature', '3.8']
title = 'Idle extension configuration and key bindings'
updated_at = <Date 2019-02-21.00:30:26.932>
user = 'https://github.com/terryjreedy'

    bugs.python.org fields:

    activity = <Date 2019-02-21.00:30:26.932>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IDLE']
creation = <Date 2014-10-23.00:17:33.672>
creator = 'terry.reedy'
dependencies = []
files = ['37550']
hgrepos = []
issue_num = 22706
keywords = ['patch']
message_count = 5.0
messages = ['229848', '232654', '232717', '232810', '336164']
nosy_count = 2.0
nosy_names = ['terry.reedy', 'Saimadhav.Heblikar']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue22706'
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.