shlex.shlex.error_leader() reports incorrect line number

未关闭
#60,325 12 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

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

调研方向

Review the shlex_test.py file and issue16121.patch linked in the issue history. Start by examining shlex.shlex.error_leader() and the existing test coverage for line reporting. Done means the reported line number is correct and the relevant test passes.

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

描述

stdlib type-bug
BPO 16121
Nosy @ezio-melotti, @bitdancer, @hoadlck
Files
  • shlex_test.py
  • issue16121.patch
    		•

    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 2012-10-03.20:10:18.120>
labels = ['type-bug', 'library']
title = 'shlex.shlex.error_leader() reports incorrect line number'
updated_at = <Date 2016-12-28.09:31:40.567>
user = 'https://bugs.python.org/Arfrever'

    bugs.python.org fields:

    activity = <Date 2016-12-28.09:31:40.567>
actor = 'petri.lehtinen'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2012-10-03.20:10:18.120>
creator = 'Arfrever'
dependencies = []
files = ['27404', '29207']
hgrepos = []
issue_num = 16121
keywords = ['patch']
message_count = 12.0
messages = ['171905', '182820', '182823', '182824', '182826', '182827', '182828', '182833', '182857', '182906', '182907', '227697']
nosy_count = 7.0
nosy_names = ['ezio.melotti', 'Arfrever', 'r.david.murray', 'zmedico', 'python-dev', 'birknilson', 'hoadlck']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue16121'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5', 'Python 3.6']

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