Should compression file-like objects provide .fileno(), misleading subprocess?

Open
#68,546 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
operating-systems

Research direction

No file or test is named. Start by examining the compression file-like objects and their interaction with subprocess file-descriptor handling, then determine the intended behavior for .fileno(); done means the behavior is agreed and covered by regression tests.

Written by the indexing model from the issue text.

Description

interpreter-core stdlib topic-IO type-feature
BPO 24358
Nosy @pitrou, @benjaminp, @jonashaag, @vadmium, @MojoVampire

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 2015-06-02.01:03:01.267>
labels = ['expert-IO']
title = 'Should compression file-like objects provide .fileno(), misleading subprocess?'
updated_at = <Date 2016-05-14.11:53:23.228>
user = 'https://github.com/MojoVampire'

bugs.python.org fields:

activity = <Date 2016-05-14.11:53:23.228>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2015-06-02.01:03:01.267>
creator = 'josh.r'
dependencies = []
files = []
hgrepos = []
issue_num = 24358
keywords = []
message_count = 7.0
messages = ['244626', '244632', '244652', '244663', '265455', '265464', '265523']
nosy_count = 6.0
nosy_names = ['pitrou', 'benjamin.peterson', 'stutzbach', 'jonash', 'martin.panter', 'josh.r']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue24358'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5', 'Python 3.6']

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.