pkgutil.get_data() is a wrapper for a deprecated class
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
docs
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 35319 |
|---|---|
| Nosy | @brettcannon |
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 2018-11-26.19:15:58.253>
labels = ['3.7', '3.8', 'type-bug', 'library', 'docs']
title = 'pkgutil.get_data() is a wrapper for a deprecated class'
updated_at = <Date 2018-11-27.23:43:17.777>
user = 'https://bugs.python.org/KevinNorris'
bugs.python.org fields:
activity = <Date 2018-11-27.23:43:17.777>
actor = 'brett.cannon'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)']
creation = <Date 2018-11-26.19:15:58.253>
creator = 'Kevin.Norris'
dependencies = []
files = []
hgrepos = []
issue_num = 35319
keywords = []
message_count = 2.0
messages = ['330456', '330561']
nosy_count = 3.0
nosy_names = ['brett.cannon', 'docs@python', 'Kevin.Norris']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue35319'
versions = ['Python 3.7', 'Python 3.8']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the pkgutil.get_data() entry point and identify the deprecated class it wraps. Read the current library documentation and issue context to determine whether the intended scope is documentation or behavior; done means the wrapper no longer presents an unresolved deprecated-class mismatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100