Allow inspecting buffering attribute of IO objects
Open
Nobody has claimed this yet.
3.7 (EOL)
topic-IO
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 30504 |
|---|---|
| Nosy | @pitrou, @benjaminp, @serhiy-storchaka |
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 2017-05-29.08:59:06.599>
labels = ['type-feature', '3.7', 'expert-IO']
title = 'Allow inspecting buffering attribute of IO objects'
updated_at = <Date 2017-05-31.16:13:25.672>
user = 'https://github.com/pitrou'
bugs.python.org fields:
activity = <Date 2017-05-31.16:13:25.672>
actor = 'pitrou'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2017-05-29.08:59:06.599>
creator = 'pitrou'
dependencies = []
files = []
hgrepos = []
issue_num = 30504
keywords = []
message_count = 3.0
messages = ['294683', '294685', '294849']
nosy_count = 4.0
nosy_names = ['pitrou', 'benjamin.peterson', 'stutzbach', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue30504'
versions = ['Python 3.7']
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
No file or test is named. Start by reading the IO component and the linked BPO issue 30504 to determine which IO objects and buffering behavior are in scope. Done means the requested buffering attribute is inspectable and the relevant behavior is 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