IDLE: Add import statement completion

Open
#61,440 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the IDLE component and BPO issue 17238, including its discussion, to determine the intended scope of import statement completion. Done should be defined as IDLE offering the agreed import completions, but the payload does not identify implementation files or tests.

Written by the indexing model from the issue text.

Description

topic-IDLE type-feature
BPO 17238
Nosy @terryjreedy, @serwy, @vadmium, @serhiy-storchaka

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 2013-02-19.15:32:51.210>
labels = ['expert-IDLE', 'type-feature', '3.10']
title = 'IDLE: Add import statement completion'
updated_at = <Date 2020-07-07.20:31:48.608>
user = 'https://bugs.python.org/RamchandraApte'

bugs.python.org fields:

activity = <Date 2020-07-07.20:31:48.608>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IDLE']
creation = <Date 2013-02-19.15:32:51.210>
creator = 'Ramchandra Apte'
dependencies = []
files = []
hgrepos = []
issue_num = 17238
keywords = []
message_count = 8.0
messages = ['182392', '191227', '191260', '271199', '271216', '271348', '370848', '373246']
nosy_count = 5.0
nosy_names = ['terry.reedy', 'roger.serwy', 'Ramchandra Apte', 'martin.panter', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17238'
versions = ['Python 3.10']

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.