Consider adding decorator for required inner class

Open
#84,926 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no files, tests, or entry points and only proposes considering a decorator for a required inner class. First clarify the intended semantics and affected library API, then locate the relevant implementation and tests. Done should include an agreed design, documented behavior, and passing coverage for the new decorator.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 40749
Nosy @erip

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 2020-05-23.23:07:34.328>
labels = ['type-feature', 'library']
title = 'Consider adding decorator for required inner class'
updated_at = <Date 2020-05-23.23:07:34.328>
user = 'https://github.com/erip'

bugs.python.org fields:

activity = <Date 2020-05-23.23:07:34.328>
actor = 'Elijah Rippeth'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-05-23.23:07:34.328>
creator = 'Elijah Rippeth'
dependencies = []
files = []
hgrepos = []
issue_num = 40749
keywords = []
message_count = 1.0
messages = ['369756']
nosy_count = 1.0
nosy_names = ['Elijah Rippeth']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue40749'
versions = []

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.