Add a pipe type (FIFO) to the io module

Open
#54,148 11 comments 0 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
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by locating Python’s io module and reviewing how its existing stream and file-like types are defined. Investigate the historical issue discussion and platform requirements for FIFO support; done means the proposed pipe type has a settled design, implementation scope, and corresponding tests.

Written by the indexing model from the issue text.

Description

stdlib topic-IO type-feature
BPO 9939
Nosy @amauryfa, @pitrou, @tiran, @benjaminp, @merwok, @vadmium, @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 2010-09-24.15:19:21.174>
labels = ['type-feature', 'library']
title = 'Add a pipe type (FIFO) to the io module'
updated_at = <Date 2015-06-15.13:47:00.129>
user = 'https://github.com/pitrou'

bugs.python.org fields:

activity = <Date 2015-06-15.13:47:00.129>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2010-09-24.15:19:21.174>
creator = 'pitrou'
dependencies = []
files = []
hgrepos = []
issue_num = 9939
keywords = []
message_count = 10.0
messages = ['117292', '117294', '117296', '117297', '117298', '117300', '117301', '117302', '117303', '117305']
nosy_count = 8.0
nosy_names = ['amaury.forgeotdarc', 'pitrou', 'christian.heimes', 'benjamin.peterson', 'stutzbach', 'eric.araujo', 'martin.panter', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue9939'
versions = ['Python 3.4']

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.