PyType_Ready doesn't ensure that all bases are ready

Open
#47,703 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start at the PyType_Ready entry point in CPython's interpreter core and review the issue's historical discussion for the intended behavior. Determine how readiness of base types should be handled, then identify or add focused interpreter-core coverage showing that all bases are ready when PyType_Ready completes.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature
BPO 3453
Nosy @ronaldoussoren, @amauryfa, @abalkin, @benjaminp

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 2008-07-27.15:14:04.037>
labels = ['interpreter-core', 'type-feature']
title = "PyType_Ready doesn't ensure that all bases are ready"
updated_at = <Date 2014-10-29.07:58:15.406>
user = 'https://bugs.python.org/rupole'

bugs.python.org fields:

activity = <Date 2014-10-29.07:58:15.406>
actor = 'pitrou'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2008-07-27.15:14:04.037>
creator = 'rupole'
dependencies = []
files = []
hgrepos = []
issue_num = 3453
keywords = []
message_count = 9.0
messages = ['70322', '70324', '70376', '70378', '70380', '71482', '107502', '193636', '230189']
nosy_count = 6.0
nosy_names = ['ronaldoussoren', 'amaury.forgeotdarc', 'belopolsky', 'rupole', 'benjamin.peterson', 'abusalimov']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue3453'
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.