pkgutil.find_loader raises an ImportError on PEP 420 implicit namespace packages

Open
#67,578 2 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
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start at the pkgutil.find_loader entry point and investigate its behavior with PEP 420 implicit namespace packages. Reproduce the reported ImportError and compare the expected namespace-package behavior; done means find_loader no longer raises ImportError for valid implicit namespace packages, with regression coverage for the case.

Written by the indexing model from the issue text.

Description

interpreter-core topic-importlib type-bug
BPO 23389
Nosy @ericvsmith, @ericsnowcurrently

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-02-03.17:55:40.140>
labels = ['interpreter-core', 'type-bug']
title = 'pkgutil.find_loader raises an ImportError on PEP 420 implicit namespace packages'
updated_at = <Date 2020-05-22.18:22:30.354>
user = 'https://bugs.python.org/alynn'

bugs.python.org fields:

activity = <Date 2020-05-22.18:22:30.354>
actor = 'brett.cannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2015-02-03.17:55:40.140>
creator = 'alynn'
dependencies = []
files = []
hgrepos = []
issue_num = 23389
keywords = []
message_count = 2.0
messages = ['235357', '235374']
nosy_count = 3.0
nosy_names = ['eric.smith', 'eric.snow', 'alynn']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue23389'
versions = ['Python 3.4']

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.