Improve repr for structseq objects to show named, but unindexed fields

Open
#55,907 14 comments 0 reactions 1 assignee View on GitHub

@pitrou is already working on this.

Since Oct 21, 2013.

Assessment

This issue has not been assessed yet.

Description

interpreter-core type-feature
BPO 11698
Nosy @rhettinger, @pitrou, @ezio-melotti, @merwok, @ericsnowcurrently, @lilydjwg, @berkerpeksag, @serhiy-storchaka, @phmc, @mblahay
Files
  • issue11698.patch
  • structseq_2.patch: Show named but unindexed fields under the dict keyword argument
    		•

    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 = 'https://github.com/pitrou'
closed_at = None
created_at = <Date 2011-03-27.22:14:56.506>
labels = ['interpreter-core', 'easy', 'type-feature', '3.8']
title = 'Improve repr for structseq objects to show named, but unindexed fields'
updated_at = <Date 2020-10-19.08:47:32.922>
user = 'https://github.com/rhettinger'

    bugs.python.org fields:

    activity = <Date 2020-10-19.08:47:32.922>
actor = 'serhiy.storchaka'
assignee = 'pitrou'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2011-03-27.22:14:56.506>
creator = 'rhettinger'
dependencies = []
files = ['26391', '32527']
hgrepos = []
issue_num = 11698
keywords = ['patch', 'easy']
message_count = 14.0
messages = ['132372', '153754', '153755', '155261', '165570', '188416', '200624', '200718', '202332', '202364', '224473', '341578', '341591', '378933']
nosy_count = 13.0
nosy_names = ['rhettinger', 'pitrou', 'ezio.melotti', 'eric.araujo', 'Arfrever', 'eric.snow', 'lilydjwg', 'berker.peksag', 'dlam', 'serhiy.storchaka', 'pconnell', 'sunfinite', 'mblahay']
pr_nums = []
priority = 'low'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue11698'
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.