-
Notifications
You must be signed in to change notification settings - Fork 184
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 fixes for master branch #3054
Conversation
- Do not attempt to install distutils in CI. - In all locations where either shutil.which() or distutils.spawn.find_executable() is used, first attempt to import shutil.which(), and disable pylint deprecated module check on the distutils import. - Locally disable too-many-positional-arguments() on a few functions. Those in "configure" will be deprecated in 3.1.0; those in "population_template" can have a more suitable fix implemented on the development branch, but for "master" branch for now the check will simply be bypassed. - pylint.rc: - Update to reflect changes to names and expected values of those settings relating to object naming. - Disable deprecated no-space-check. - Fix overgeneral-exceptions.
Module is only loaded in the absence of shlex.quote(). This import syntax should ideally be removed entirely upon merge to development branch for inclusion in 3.1.0.
Package "python2" no longer available in GitHub CI Action.
2d6d9bc
to
c5c41a8
Compare
While c5c41a8 is unrelated to |
c5c41a8
to
7ed0a5d
Compare
4bb17f1
to
abe2a43
Compare
Requires a renewed review; merge failed due to needing to re-run |
06f92b4
to
049bf05
Compare
Sorry, need another one; forgot to run |
#3052 is failing CI for multiple reasons. One of them is errors during
pylint
testing, presumably due to thepylint
version on the Action being incremented. Here I have addressed those issues onmaster
, as well as some other Errors thatpylint
raised on my own system when checkingmaster
.Some changes are due to warnings about reading from uninitialised variables, which arise due to using a "
elif variable == 'string'
" substitute-for-switch
pattern that is not guaranteed to be exhaustive from the perspective of the linter. I tend to prefer to keep that pattern rather than using an "else:
" for the last option as it's more robust to future augmentation.I have not addressed the warning about
distutils
being deprecated.On my local system I also get a lot of these, will wait to see if GitHub complains about it also: