pylint-dev/pylint

Incorrect Recommendation for unnecessary-lambda

Open

#9,317 opened on Dec 18, 2023

View on GitHub
 (2 comments) (0 reactions) (1 assignee)Python (1,059 forks)batch import
Documentation :green_book:Good first issueHacktoberfestHelp wanted 🙏Needs investigation 🔬

Repository metrics

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

Description

https://github.com/pylint-dev/pylint/blob/278de0f43e389142d14d2ba2a47b770c2d84a085/doc/data/messages/u/unnecessary-lambda/good/pandas.py#L1C7-L1C7

Turns out this doesn't seem to be valid, because python interprets str in df.apply(str) as a type instead of a method. At least this is the case in 3.10+

Contributor guide

Research direction
Investigate the unnecessary lambda rule in pylint to understand why it incorrectly recommends replacing `df.apply(str)` with `df.apply(str)`. Focus on how Python 3.10+ handles `str` as a type vs callable. Check the rule's logic and test cases.
Tech stack
python
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70