pyclbr module needs to be more flexible on loader support

Open
#70,771 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by locating the pyclbr module in the CPython library and reading how it currently handles loaders. The issue does not identify supported loader types, target files, or tests, so clarify the expected loader behavior before defining completion.

Written by the indexing model from the issue text.

Description

stdlib topic-importlib type-bug
BPO 26584
Nosy @terryjreedy, @ncoghlan, @ericsnowcurrently, @isidentical

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-17.18:20:00.045>
labels = ['type-bug', 'library']
title = 'pyclbr module needs to be more flexible on loader support'
updated_at = <Date 2020-11-05.00:38:28.143>
user = 'https://github.com/ericsnowcurrently'

bugs.python.org fields:

activity = <Date 2020-11-05.00:38:28.143>
actor = 'BTaskaya'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-03-17.18:20:00.045>
creator = 'eric.snow'
dependencies = []
files = []
hgrepos = []
issue_num = 26584
keywords = []
message_count = 1.0
messages = ['261924']
nosy_count = 4.0
nosy_names = ['terry.reedy', 'ncoghlan', 'eric.snow', 'BTaskaya']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26584'
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.