Add a PyCF_DISPLAY_EXPRESSION_RESULTS flag

Open
#60,853 4 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
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start by reading the linked BPO issue 16649 and the CPython interpreter-core flag-handling entry points; the payload names no files or tests. Clarify the intended behavior and integration points for PyCF_DISPLAY_EXPRESSION_RESULTS, then identify the relevant tests and update them so the flag's behavior is covered.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature
BPO 16649
Nosy @ncoghlan, @kristjanvalur, @benjaminp, @nanjekyejoannah, @isidentical

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 2012-12-09.06:34:28.759>
labels = ['interpreter-core', 'type-feature']
title = 'Add a PyCF_DISPLAY_EXPRESSION_RESULTS flag'
updated_at = <Date 2019-12-01.12:13:25.596>
user = 'https://github.com/ncoghlan'

bugs.python.org fields:

activity = <Date 2019-12-01.12:13:25.596>
actor = 'BTaskaya'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2012-12-09.06:34:28.759>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 16649
keywords = []
message_count = 3.0
messages = ['177199', '177223', '177245']
nosy_count = 6.0
nosy_names = ['ncoghlan', 'kristjan.jonsson', 'benjamin.peterson', 'aliles', 'nanjekyejoannah', 'BTaskaya']
pr_nums = []
priority = 'low'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue16649'
versions = ['Python 3.4']

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.