python / python/cpython

Deprecate legacy introspection APIs in the inspect module

Open
#76,371 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.13 docs type-feature
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 32190
Nosy @brettcannon, @ncoghlan

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 2017-12-01.05:22:05.533>
labels = ['type-feature', '3.7', 'docs']
title = 'Separate out legacy introspection APIs in the inspect docs'
updated_at = <Date 2017-12-01.05:22:05.533>
user = 'https://github.com/ncoghlan'

bugs.python.org fields:

activity = <Date 2017-12-01.05:22:05.533>
actor = 'ncoghlan'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2017-12-01.05:22:05.533>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 32190
keywords = []
message_count = 1.0
messages = ['307362']
nosy_count = 3.0
nosy_names = ['brett.cannon', 'ncoghlan', 'docs@python']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue32190'
versions = ['Python 3.6', 'Python 3.7']

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.

Research direction

Start with the inspect module documentation and the legacy introspection APIs referenced by the issue. Clarify which APIs need deprecation treatment and reorganize or update their documentation; done means the legacy interfaces are clearly identified and the inspect docs reflect their status.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.