Skip to content

Conversation

@zenlyj
Copy link
Contributor

@zenlyj zenlyj commented Jun 22, 2025

Type of Changes

Type
βœ“ πŸ› Bug fix
✨ New feature
πŸ”¨ Refactoring
πŸ“œ Docs

Description

The issue lies in the predicate for variable annotations. It currently checks whether a Name node is a child of an AnnAssign node, but it should also check whether the Name node is used as type annotation.

Closes #10421

@zenlyj zenlyj added the False Negative πŸ¦‹ No message is emitted but something is wrong with the code label Jun 22, 2025
@Pierre-Sassoulas Pierre-Sassoulas added this to the 4.0.0 milestone Jun 22, 2025
Copy link
Member

@Pierre-Sassoulas Pierre-Sassoulas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@codecov
Copy link

codecov bot commented Jun 22, 2025

Codecov Report

βœ… All modified and coverable lines are covered by tests.
βœ… Project coverage is 95.88%. Comparing base (f5aa766) to head (646b503).
⚠️ Report is 109 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main   #10437   +/-   ##
=======================================
  Coverage   95.88%   95.88%           
=======================================
  Files         176      176           
  Lines       19140    19140           
=======================================
  Hits        18352    18352           
  Misses        788      788           
Files with missing lines Coverage Ξ”
pylint/checkers/variables.py 97.29% <100.00%> (ΓΈ)
πŸš€ New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions

This comment has been minimized.

@zenlyj
Copy link
Contributor Author

zenlyj commented Jun 22, 2025

Went through primer results, this probably needs to be refined. will make an update soon

@zenlyj zenlyj changed the title Fix possibly-used-before-assignment false negative for type-annotated assignation Fix possibly-used-before-assignment false negative for type-annotated assignment Jun 23, 2025
@github-actions
Copy link
Contributor

πŸ€– According to the primer, this change has no effect on the checked open source code. πŸ€–πŸŽ‰

This comment was generated for commit 646b503

Copy link
Member

@Pierre-Sassoulas Pierre-Sassoulas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In 4.0.0 it goes !

@Pierre-Sassoulas Pierre-Sassoulas merged commit d9927e4 into pylint-dev:main Jun 24, 2025
40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

False Negative πŸ¦‹ No message is emitted but something is wrong with the code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

False negative: possibly-used-before-assignment with type annotation after assignment in conditional/loop

3 participants