Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix possibly-used-before-assignment issues in our own codebase #9637

Open
jacobtylerwalls opened this issue May 16, 2024 · 0 comments · May be fixed by #9644
Open

Fix possibly-used-before-assignment issues in our own codebase #9637

jacobtylerwalls opened this issue May 16, 2024 · 0 comments · May be fixed by #9644
Labels
Good first issue Friendly and approachable by new contributors Maintenance Discussion or action around maintaining pylint or the dev workflow Needs PR This issue is accepted, sufficiently specified and now needs an implementation

Comments

@jacobtylerwalls
Copy link
Member

jacobtylerwalls commented May 16, 2024 •
edited

This new check was turned off for pylint itself with the intent to just get the check out the door. A PR to improve the pylint codebase and enable the check would be welcome.
@jacobtylerwalls jacobtylerwalls added Good first issue Friendly and approachable by new contributors Needs PR This issue is accepted, sufficiently specified and now needs an implementation Maintenance Discussion or action around maintaining pylint or the dev workflow labels May 16, 2024
This was referenced May 17, 2024
Open
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Good first issue Friendly and approachable by new contributors Maintenance Discussion or action around maintaining pylint or the dev workflow Needs PR This issue is accepted, sufficiently specified and now needs an implementation
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix possibly-used-before-assignment issues in pylint codebase aatle/pylint
1 participant
@jacobtylerwalls