Add new format of fixed length string for PyErr_Format

Open
#64,183 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names the PyErr_Format entry point and the historical add_T_format_for_PyErr_Format.patch, with further context in BPO issue 19984. Start by reviewing those references and locating the corresponding CPython implementation and tests. Done means the fixed-length string format is supported with coverage for its expected behavior.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature
BPO 19984
Nosy @warsaw, @pitrou, @serhiy-storchaka, @vajrasky
Files
  • add_T_format_for_PyErr_Format.patch
    		•

    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 2013-12-15.05:23:22.415>
labels = ['interpreter-core', 'type-feature', '3.10']
title = 'Add new format of fixed length string for PyErr_Format'
updated_at = <Date 2021-02-15.20:05:44.863>
user = 'https://github.com/vajrasky'

    bugs.python.org fields:

    activity = <Date 2021-02-15.20:05:44.863>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2013-12-15.05:23:22.415>
creator = 'vajrasky'
dependencies = []
files = ['33142']
hgrepos = []
issue_num = 19984
keywords = ['patch']
message_count = 2.0
messages = ['206216', '206232']
nosy_count = 4.0
nosy_names = ['barry', 'pitrou', 'serhiy.storchaka', 'vajrasky']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue19984'
versions = ['Python 3.10']

    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.