Downgrade pylint
and remove pylint
CI workflow
#107
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context for changes
Downgrade
pylint
to v2.13.5 to allow the use of theno-self-use
flag in unit tests and removepylint
CI workflow as this is covered by code-factor.Example usage and tests
Performance results justifying changes
Workflow actions and tests
Expected benefits and drawbacks
Expected benefits:
pylint
check.Possible drawbacks:
pylint
action to the CI workflow.Related Github issues
Checklist and integration statements
black
,docformatter
andpylint
configurations.README.md
as needed.CHANGELOG.md
following the template. I recognize that the developers may revisitCHANGELOG.md
and the versioning, and create a Special Release including my changes.