MSVCRT's spawnve/spawnvpe are not thread safe

未关闭
#50,725 6 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
15/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
python
领域
operating-systems

调研方向

Start with the attached spawnve.py failing sample and its workaround, then review the linked BPO issue 6476 and its discussion about MSVCRT's spawnve/spawnvpe. The payload records a wont-fix resolution and no pull request, so there is no defined accepted change or completion test to follow.

由索引模型根据 Issue 内容生成。

描述

interpreter-core type-bug
BPO 6476
Nosy @amauryfa, @pitrou
Files
  • spawnve.py: Failing sample with workaround
    		•

    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 2009-07-13.17:11:07.624>
labels = ['interpreter-core', 'type-bug']
title = "MSVCRT's spawnve/spawnvpe are not thread safe"
updated_at = <Date 2011-07-18.23:31:30.590>
user = 'https://bugs.python.org/jfonseca'

    bugs.python.org fields:

    activity = <Date 2011-07-18.23:31:30.590>
actor = 'pitrou'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2009-07-13.17:11:07.624>
creator = 'jfonseca'
dependencies = []
files = ['14495']
hgrepos = []
issue_num = 6476
keywords = []
message_count = 6.0
messages = ['90495', '90498', '90503', '140574', '140632', '140634']
nosy_count = 5.0
nosy_names = ['amaury.forgeotdarc', 'pitrou', 'jfonseca', 'python-dev', 'steve_hill']
pr_nums = []
priority = 'normal'
resolution = 'wont fix'
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue6476'
versions = ['Python 2.7', 'Python 3.2', 'Python 3.3']

    主要语言
    Python
    星标
    77.2k
    派生
    36k
    平均合并
    1 天 9 小时
    30 天内合并 PR
    558

    贡献指南

    打开贡献指南

    从这里开始

    1. 先读完整个 Issue，再读项目的贡献指南。
    2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
    3. Fork 仓库，在一个分支上完成修改。
    4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

    python/cpython 的其他 Issue

    查看 python/cpython 的全部 Issue

    相似的 Issue

    更多 Python Issue

    把新 issue 发到你的邮箱

    精选适合新手参与的 GitHub issue 摘要。