pylint-dev/pylint

Use inference to determine if **kwargs is missing a named parameter

Open

#8,785 创建于 2023年6月18日

在 GitHub 查看
 (4 评论) (0 反应) (0 负责人)Python (4,978 star) (1,059 fork)batch import
False Negative 🦋Good first issueHacktoberfestNeeds PR

描述

I would expect these two lines to raise the same set of messages. We don't use inference to analyze whether **kwargs contains the missing named parameter x. We could.

import copy
import os

copy.copy(**{"y": os.environ})  # [unexpected-keyword-arg]
copy.copy(y=os.environ)  # [no-value-for-parameter, unexpected-keyword-arg]

False negative for no-value-for-parameter.

贡献者指南

技术栈
python
领域
backendtoolingdeveloper experience
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Pythonpylint internalsinference engine
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Investigate how pylint currently handles **kwargs in function calls. The issue points to a false negative for 'no value for parameter' when using **kwargs. Look at the codebase for inference logic related to keyword argument unpacking, likely in the checker for variable arguments. Consider how inference could be improved to detect missing named parameters when **kwargs is used. Relevant files may include pylint/checkers/typecheck.py or similar inference modules.