Which are reasonable reason for recursion limit in function _vformat of class Formatter lib string?

Open
#77,453 2 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
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reading lib/string.py, focusing on Formatter._vformat and the recursion behavior described in the issue. Determine whether the expected outcome is a code change, documentation, or only an explanation; the work is complete when the reasonable recursion-limit behavior and any required coverage are clearly established.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 33272
Nosy @ericvsmith

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 2018-04-13.11:12:03.745>
labels = ['type-bug', 'library']
title = 'Which are reasonable reason for recursion limit in function _vformat of class Formatter lib string?'
updated_at = <Date 2018-04-13.11:41:47.879>
user = 'https://bugs.python.org/mvgavrilov'

bugs.python.org fields:

activity = <Date 2018-04-13.11:41:47.879>
actor = 'eric.smith'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-04-13.11:12:03.745>
creator = 'mv.gavrilov'
dependencies = []
files = []
hgrepos = []
issue_num = 33272
keywords = []
message_count = 1.0
messages = ['315242']
nosy_count = 2.0
nosy_names = ['eric.smith', 'mv.gavrilov']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue33272'
versions = ['Python 3.6']

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.