unittest discover should recurse into packages which are already in sys.path

Open
#55,892 5 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
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

The issue names the unittest discover entry point but no source file or test. Start by locating its package-discovery implementation and existing discovery tests, then reproduce behavior with a package already present in sys.path. Done means discovery recurses into that package while preserving existing discovery behavior.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 11683
Nosy @ezio-melotti, @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 2011-03-26.14:36:41.287>
labels = ['type-feature']
title = 'unittest discover should recurse into packages which are already in sys.path'
updated_at = <Date 2011-03-26.22:58:09.579>
user = 'https://bugs.python.org/CalvinSpealman'

bugs.python.org fields:

activity = <Date 2011-03-26.22:58:09.579>
actor = 'michael.foord'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2011-03-26.14:36:41.287>
creator = 'Calvin.Spealman'
dependencies = []
files = []
hgrepos = []
issue_num = 11683
keywords = []
message_count = 5.0
messages = ['132242', '132271', '132274', '132279', '132280']
nosy_count = 3.0
nosy_names = ['ezio.melotti', 'michael.foord', 'Calvin.Spealman']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue11683'
versions = ['Python 3.3']

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.