test_cmd_line_script should include namespace package tests

Open
#59,576 2 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
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

Locate the test_cmd_line_script test entry point and read the existing command-line script test cases first. Add coverage for namespace package tests, then run the relevant test module and confirm those cases are included and pass.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 15371
Nosy @ncoghlan, @nanjekyejoannah

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 2012-07-16.14:27:56.777>
labels = ['library']
title = 'test_cmd_line_script should include namespace package tests'
updated_at = <Date 2019-08-07.12:59:49.322>
user = 'https://github.com/ncoghlan'

bugs.python.org fields:

activity = <Date 2019-08-07.12:59:49.322>
actor = 'nanjekyejoannah'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2012-07-16.14:27:56.777>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 15371
keywords = []
message_count = 2.0
messages = ['165614', '228274']
nosy_count = 2.0
nosy_names = ['ncoghlan', 'nanjekyejoannah']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue15371'
versions = ['Python 3.4', 'Python 3.5']

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.