shlex not posix compliant when parsing "foo#bar"

未关闭
#51,860 8 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
cli

调研方向

Start with the linked lexer_test.py test and inspect the shlex_posix.diff patch to understand the expected handling of "foo#bar". Trace the relevant shlex parsing behavior, then update the regression coverage so it captures POSIX-compliant behavior and verify the shlex tests pass.

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

描述

stdlib type-feature
BPO 7611
Nosy @terryjreedy, @merwok, @meadori
Files
  • lexer_test.py: test to show shlex behaviour
  • shlex_posix.diff
    		•

    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-12-31.08:42:42.098>
labels = ['type-feature', 'library', '3.9', '3.10']
title = 'shlex not posix compliant when parsing "foo#bar"'
updated_at = <Date 2020-11-11.17:08:24.800>
user = 'https://bugs.python.org/jjdmol2'

    bugs.python.org fields:

    activity = <Date 2020-11-11.17:08:24.800>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2009-12-31.08:42:42.098>
creator = 'jjdmol2'
dependencies = []
files = ['15709', '15718']
hgrepos = []
issue_num = 7611
keywords = ['patch']
message_count = 7.0
messages = ['97081', '97082', '97125', '112740', '148270', '148292', '148456']
nosy_count = 6.0
nosy_names = ['terry.reedy', 'ferringb', 'eric.araujo', 'meador.inge', 'jjdmol2', 'cadf']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue7611'
versions = ['Python 3.9', 'Python 3.10']

    主要语言
    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 摘要。