`pkgutil.get_data` causes future imports of children modules to fail.

Open
#85,691 3 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
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start with the pkgutil.get_data entry point and the linked pkgutil_err.tar package, then reproduce the failure involving future imports of child modules. Trace the import behavior around that reproduction; done means accessing package data no longer prevents later child-module imports from succeeding.

Written by the indexing model from the issue text.

Description

3.7 (EOL) 3.8 (EOL) stdlib type-bug
BPO 41519
Nosy @warsaw, @brettcannon, @pganssle, @corynezin
Files
  • pkgutil_err.tar: Package to reproduce errors
    		•

    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 2020-08-10.20:37:28.031>
labels = ['3.7', '3.8', 'type-bug', 'library']
title = '`pkgutil.get_data` causes future imports of children modules to fail.'
updated_at = <Date 2020-09-29.20:56:54.943>
user = 'https://github.com/corynezin'

    bugs.python.org fields:

    activity = <Date 2020-09-29.20:56:54.943>
actor = 'cnezin'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-08-10.20:37:28.031>
creator = 'cnezin'
dependencies = []
files = ['49381']
hgrepos = []
issue_num = 41519
keywords = []
message_count = 3.0
messages = ['375149', '377679', '377682']
nosy_count = 4.0
nosy_names = ['barry', 'brett.cannon', 'p-ganssle', 'cnezin']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41519'
versions = ['Python 3.6', 'Python 3.7', '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.