pylint-dev/pylint

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

Open

#8,785 opened on Jun 18, 2023

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Python (1,059 forks)batch import
False Negative 🦋Good first issueHacktoberfestNeeds PR

Repository metrics

Stars
 (4,978 stars)
PR merge metrics
 (Avg merge 12h 9m) (29 merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Investigate how pylint's inference of **kwargs works for missing named parameters and update the check for 'no value for parameter' to consider **kwargs.
Tech stack
python
Domain
tooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Pythonpylint internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50