PyRun_SimpleFile should provide a version that does not need a FILE*

Open
#82,025 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api, operating-systems

Research direction

Start with the PyRun_SimpleFile entry point and the Windows component context described in the issue. Determine the API shape for an equivalent version that does not require a FILE*, then identify how its behavior should be validated. Done means the new public entry point supports the requested use case without requiring a FILE*.

Written by the indexing model from the issue text.

Description

OS-windows pending type-feature
BPO 37844
Nosy @pfmoore, @tjguk, @zware, @zooba, @cbiesinger

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 2019-08-13.18:21:40.506>
labels = ['type-feature', 'OS-windows']
title = 'PyRun_SimpleFile should provide a version that does not need a FILE*'
updated_at = <Date 2021-09-11.10:46:47.983>
user = 'https://github.com/cbiesinger'

bugs.python.org fields:

activity = <Date 2021-09-11.10:46:47.983>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2019-08-13.18:21:40.506>
creator = 'cbiesinger'
dependencies = []
files = []
hgrepos = []
issue_num = 37844
keywords = []
message_count = 1.0
messages = ['349598']
nosy_count = 5.0
nosy_names = ['paul.moore', 'tim.golden', 'zach.ware', 'steve.dower', 'cbiesinger']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue37844'
versions = []

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.