Come up with a good way to handle module aliasing

Open
#69,835 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
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

No files, tests, or implementation entry points are identified. Start by reading the linked BPO issue 25649 and its discussion to determine the intended module-aliasing behavior and affected library area. The issue needs a concrete scope and an agreed definition of done before implementation can begin.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 25649
Nosy @warsaw, @brettcannon

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-11-17.17:07:40.296>
labels = ['type-feature', 'library']
title = 'Come up with a good way to handle module aliasing'
updated_at = <Date 2015-11-17.17:15:47.803>
user = 'https://github.com/brettcannon'

bugs.python.org fields:

activity = <Date 2015-11-17.17:15:47.803>
actor = 'barry'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-11-17.17:07:40.296>
creator = 'brett.cannon'
dependencies = []
files = []
hgrepos = []
issue_num = 25649
keywords = []
message_count = 2.0
messages = ['254805', '254806']
nosy_count = 2.0
nosy_names = ['barry', 'brett.cannon']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue25649'
versions = ['Python 3.6']

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.