h5py not playing nicely with subprocess and mpirun
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39445 |
|---|
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 2020-01-24.18:21:59.774>
labels = ['3.7', 'type-bug', 'library']
title = 'h5py not playing nicely with subprocess and mpirun'
updated_at = <Date 2020-01-24.18:21:59.774>
user = 'https://bugs.python.org/RafaelLaboissire'
bugs.python.org fields:
activity = <Date 2020-01-24.18:21:59.774>
actor = 'Rafael Laboissi\xc3\xa8re'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-01-24.18:21:59.774>
creator = 'Rafael Laboissi\xc3\xa8re'
dependencies = []
files = []
hgrepos = []
issue_num = 39445
keywords = []
message_count = 1.0
messages = ['360638']
nosy_count = 1.0
nosy_names = ['Rafael Laboissi\xc3\xa8re']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39445'
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
The issue names no files, tests, or reproduction steps; begin by obtaining a minimal h5py/subprocess/mpirun reproduction. Identify the affected CPython library entry point and a regression test before scoping the change. Done should mean the reproduced failure is resolved and covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100