Define instance mutability explicitly on type objects?

Open
#69,179 8 comments 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
compilers

Research direction

No files, tests, or entry points are named. Start by reading the linked BPO issue 24991 and its seven recorded messages, then review the interpreter-core implementation and Python 3.8 expectations. Done is not defined; clarify the desired mutability model and acceptance tests before coding.

Written by the indexing model from the issue text.

Description

3.8 (EOL) interpreter-core type-feature
BPO 24991
Nosy @rhettinger, @ncoghlan, @tpn, @njsmith, @eltoder, @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 2015-09-03.06:08:03.336>
labels = ['interpreter-core', 'type-feature', '3.8']
title = 'Define instance mutability explicitly on type objects?'
updated_at = <Date 2017-12-25.23:58:24.159>
user = 'https://github.com/ncoghlan'

bugs.python.org fields:

activity = <Date 2017-12-25.23:58:24.159>
actor = 'ncoghlan'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2015-09-03.06:08:03.336>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 24991
keywords = []
message_count = 7.0
messages = ['249605', '249612', '249706', '250289', '307934', '307971', '309047']
nosy_count = 7.0
nosy_names = ['rhettinger', 'ncoghlan', 'trent', 'Arfrever', 'njs', 'eltoder', 'eric.snow']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue24991'
versions = ['Python 3.8']

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.