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 #716

Closed
evidencebp opened this issue Nov 26, 2024 · 2 comments
Closed

Pylint alerts corrections as part of an intervention experiment #716

evidencebp opened this issue Nov 26, 2024 · 2 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 34 interventions in 31 files
The interventions will be of the following types:
line-too-long: 31
unnecessary-pass: 1
wildcard-import: 2

May I do the interventions, @evanepio?

@evanepio
Copy link
Owner

Sorry for the delay in response.

I don't think my project would be a good fit for your study. This project hasn't changed in years. Sure I've updated dependencies, but I have not enhanced or added features to it. I won't be able to give you an answer as to whether or not the linting helped. The existing bugs are unlikely to be discovered, and no new bugs are likely to get introduced when all I do is update dependencies.

A second reason why is that I already have my code linted using the ruff tool. And the files that would be affected by any intervention are mostly set to be ignored (generated database migration files). My line length is explicitly set to allow 120 characters (line 90 of pyproject.toml does this) so it's incompatible with the pylint settings your study has chosen. Pylint also missed my third wild-card import, so the settings might be off.

My apologies, and best of luck with your study. It sounds really cool and other projects will be able to benefit!

@evidencebp
Copy link
Author

You are right, @evanepio.
I indeed need a project that is still in development in order to evaluate the impact on behavior.

Thank you for your time and attention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants