readline completer could return an iterable

Open
#58,154 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

No source file or test is named in the issue. Start by reviewing the readline completer API and its existing tests, then determine the compatibility and protocol requirements for allowing an iterable return value; done should include documented behavior and regression coverage.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 13946
Nosy @MojoVampire

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 2012-02-05.19:48:01.208>
labels = ['type-feature', 'library']
title = 'readline completer could return an iterable'
updated_at = <Date 2019-03-16.00:13:17.677>
user = 'https://bugs.python.org/nicolas49'

bugs.python.org fields:

activity = <Date 2019-03-16.00:13:17.677>
actor = 'BreamoreBoy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2012-02-05.19:48:01.208>
creator = 'nicolas_49'
dependencies = []
files = []
hgrepos = []
issue_num = 13946
keywords = []
message_count = 3.0
messages = ['152703', '222161', '222253']
nosy_count = 2.0
nosy_names = ['nicolas_49', 'josh.r']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue13946'
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.