Accelerate string.Template by using formatted string literals
Open
Nobody has claimed this yet.
easy
performance
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 28309 |
|---|---|
| Nosy | @birkenfeld, @ericvsmith, @serhiy-storchaka |
| Files |
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 2016-09-29.09:01:25.978>
labels = ['3.7', 'library', 'performance']
title = 'Accelerate string.Template by using formatted string literals'
updated_at = <Date 2016-09-29.09:02:14.892>
user = 'https://github.com/serhiy-storchaka'
bugs.python.org fields:
activity = <Date 2016-09-29.09:02:14.892>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-09-29.09:01:25.978>
creator = 'serhiy.storchaka'
dependencies = []
files = ['44878']
hgrepos = []
issue_num = 28309
keywords = ['patch']
message_count = 1.0
messages = ['277690']
nosy_count = 3.0
nosy_names = ['georg.brandl', 'eric.smith', 'serhiy.storchaka']
pr_nums = []
priority = 'low'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue28309'
versions = ['Python 3.7']
- PR: gh-99177
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked faster_template.patch and PR gh-99177, then check the current string.Template implementation and its status in the repository. Done means the proposed acceleration is either completed and validated in the current codebase or the existing pull request is updated with any remaining work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 15/100