add FileInput.rollback() for in-place filters
Open
Nobody has claimed this yet.
3.10
3.11
3.9 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44882 |
|---|
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 2021-08-10.22:22:25.243>
labels = ['type-feature', 'library', '3.9', '3.10', '3.11']
title = 'add FileInput.rollback() for in-place filters'
updated_at = <Date 2021-08-10.22:29:22.249>
user = 'https://bugs.python.org/samwyse'
bugs.python.org fields:
activity = <Date 2021-08-10.22:29:22.249>
actor = 'samwyse'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-08-10.22:22:25.243>
creator = 'samwyse'
dependencies = []
files = []
hgrepos = []
issue_num = 44882
keywords = []
message_count = 1.0
messages = ['399361']
nosy_count = 1.0
nosy_names = ['samwyse']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue44882'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
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
The issue names FileInput.rollback() but does not identify an implementation file, tests, or the expected rollback semantics. Start by locating FileInput in the standard library and reviewing its current in-place filtering behavior; the work is done when the intended rollback API and its behavior are covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100