unittest.__init__:main shadows unittest.main

Open
#67,047 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the unittest.init and unittest.main definitions and read the existing issue discussion, since no source files or tests are named. Confirm how the name collision occurs and identify the expected public behavior before making a change; done means the shadowing is resolved and relevant unittest tests pass.

Written by the indexing model from the issue text.

Description

3.11 stdlib type-bug
BPO 22858
Nosy @pitrou, @rbtcollins, @ezio-melotti, @bitdancer, @voidspace

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 2014-11-13.10:23:24.339>
labels = ['type-bug', 'library', '3.11']
title = 'unittest.__init__:main shadows unittest.main'
updated_at = <Date 2021-12-12.00:26:56.697>
user = 'https://github.com/rbtcollins'

bugs.python.org fields:

activity = <Date 2021-12-12.00:26:56.697>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-11-13.10:23:24.339>
creator = 'rbcollins'
dependencies = []
files = []
hgrepos = []
issue_num = 22858
keywords = []
message_count = 9.0
messages = ['231101', '231119', '231139', '231440', '246706', '246738', '246751', '246771', '246772']
nosy_count = 5.0
nosy_names = ['pitrou', 'rbcollins', 'ezio.melotti', 'r.david.murray', 'michael.foord']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue22858'
versions = ['Python 3.11']

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.