Lazy Literal String Interpolation (PEP-498-based fl-strings)

Open
#77,135 10 comments 12 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start with the linked BPO issue 32954 and its nine-message discussion to understand the proposed PEP-498-based fl-strings behavior. The issue names no files or tests; done would require an agreed specification plus the corresponding interpreter implementation and tests.

Written by the indexing model from the issue text.

Description

3.7 (EOL) 3.8 (EOL) interpreter-core type-feature
BPO 32954
Nosy @warsaw, @ericvsmith, @serhiy-storchaka, @arcivanov, @mbdevpl

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-02-26.10:19:19.626>
labels = ['interpreter-core', '3.8', 'type-feature', '3.7']
title = 'Lazy Literal String Interpolation (PEP-498-based fl-strings)'
updated_at = <Date 2019-12-18.06:25:31.673>
user = 'https://github.com/arcivanov'

bugs.python.org fields:

activity = <Date 2019-12-18.06:25:31.673>
actor = 'mbdevpl'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2018-02-26.10:19:19.626>
creator = 'arcivanov'
dependencies = []
files = []
hgrepos = []
issue_num = 32954
keywords = []
message_count = 9.0
messages = ['312909', '312910', '312911', '312912', '312913', '312914', '312918', '312922', '312923']
nosy_count = 5.0
nosy_names = ['barry', 'eric.smith', 'serhiy.storchaka', 'arcivanov', 'mbdevpl']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue32954'
versions = ['Python 3.7', '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.