Deprecate portions or all of pkgutil module.

Open
#64,138 9 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start with the pkgutil module and the linked BPO 19939 discussion. The issue does not identify which portions should be deprecated, nor does it name files or tests. The work is not ready for a newcomer until the deprecation scope and completion criteria are agreed.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 19939
Nosy @brettcannon, @pjeby, @ncoghlan, @ericsnowcurrently

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 2013-12-10.05:54:41.796>
labels = ['type-feature', 'library']
title = 'Deprecate portions or all of pkgutil module.'
updated_at = <Date 2013-12-10.15:11:15.442>
user = 'https://github.com/ericsnowcurrently'

bugs.python.org fields:

activity = <Date 2013-12-10.15:11:15.442>
actor = 'brett.cannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-12-10.05:54:41.796>
creator = 'eric.snow'
dependencies = []
files = []
hgrepos = []
issue_num = 19939
keywords = []
message_count = 3.0
messages = ['205771', '205778', '205823']
nosy_count = 5.0
nosy_names = ['brett.cannon', 'pje', 'ncoghlan', 'Arfrever', 'eric.snow']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue19939'
versions = ['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.