Allow built-in module in package

Open
#70,833 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend, build-system

Research direction

Start by reading the attached builtin_package.patch, importlib_h.patch, and test_builtin_submodule.py, then inspect the related interpreter and build areas in the current tree. Run the referenced test after understanding the proposed behavior. Done means the built-in module can be used within a package and the regression test passes.

Written by the indexing model from the issue text.

Description

build interpreter-core type-feature
BPO 26646
Nosy @brettcannon, @ncoghlan, @ericsnowcurrently
Files
  • builtin_package.patch: Patch for everything except the importlib.h changes
  • importlib_h.patch: The importlib.h changes
  • test_builtin_submodule.py
    		•

    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 2016-03-26.20:20:28.345>
labels = ['interpreter-core', 'type-feature', 'build']
title = 'Allow built-in module in package'
updated_at = <Date 2016-04-01.22:14:54.465>
user = 'https://bugs.python.org/DanielShaulov'

    bugs.python.org fields:

    activity = <Date 2016-04-01.22:14:54.465>
actor = 'brett.cannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build', 'Interpreter Core']
creation = <Date 2016-03-26.20:20:28.345>
creator = 'Daniel Shaulov'
dependencies = []
files = ['42297', '42298', '42350']
hgrepos = []
issue_num = 26646
keywords = ['patch']
message_count = 4.0
messages = ['262495', '262529', '262775', '262777']
nosy_count = 4.0
nosy_names = ['brett.cannon', 'ncoghlan', 'eric.snow', 'Daniel Shaulov']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue26646'
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.