python / python/cpython

How to search for a __main__ module using pyclbr in Python3?

Open
#87,413 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.8 (EOL) stdlib topic-importlib type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 43247
Nosy @kxrob, @kebab-mai-haddi

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 2021-02-18.03:16:48.716>
labels = ['3.8', 'type-bug', 'library']
title = 'How to search for a __main__ module using pyclbr in Python3?'
updated_at = <Date 2021-03-01.22:00:10.867>
user = 'https://github.com/kebab-mai-haddi'

bugs.python.org fields:

activity = <Date 2021-03-01.22:00:10.867>
actor = 'kebab-mai-haddi'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-02-18.03:16:48.716>
creator = 'kebab-mai-haddi'
dependencies = []
files = []
hgrepos = []
issue_num = 43247
keywords = []
message_count = 3.0
messages = ['387200', '387524', '387882']
nosy_count = 2.0
nosy_names = ['kxrob', 'kebab-mai-haddi']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue43247'
versions = ['Python 3.8']

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.

Research direction

The report only names pyclbr and the main module; no source file, test, or reproducer is provided. Start by reading the pyclbr library implementation and its existing tests, then define the expected Python 3 lookup behavior. Done means the behavior is resolved and covered by an appropriate test or documentation update.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.