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.

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

Pylint alerts corrections as part of an intervention experiment #187

Closed
evidencebp opened this issue Nov 27, 2024 · 0 comments
Closed

Pylint alerts corrections as part of an intervention experiment #187

evidencebp opened this issue Nov 27, 2024 · 0 comments

Comments

@evidencebp
Copy link

Pylint alerts are correlated with tendency to bugs and harder maintenance.
I'd like to conduct a software engineering experiment regarding the benefit of Pylint alerts removal.
The experiment is described here.

In the experiments, Pylint is used with some specific alerts, files are selected for intervention and control.
After the interventions are done, one can wait and examine the results.

Your repository is expected to benefit from the interventions.
I'm asking for your approval for conducting an intervention in your repository.

See examples of interventions in stanford-oval/storm, gabfl/vault, and coreruleset/coreruleset.

You can see the planed interventions
The plan is to do 60 interventions in 42 files
The interventions will be of the following types:
line-too-long: 54
simplifiable-if-expression: 1
too-many-branches: 1
too-many-return-statements: 2
too-many-statements: 1
wildcard-import: 1

May I do the interventions?

@deanlinssen deanlinssen closed this as not planned Won't fix, can't repro, duplicate, stale Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants