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

Fix failing builds due to pylint 2.4.0 update #923

Merged
merged 2 commits into from
Sep 24, 2019

Conversation

lukpueh
Copy link
Member

@lukpueh lukpueh commented Sep 24, 2019

Fixes issue #:
None.

Description of the changes being introduced by the pull request:
Pylint was updated to 2.4.0 a few minutes ago. The new versions now emits the following warnings:

py35 run-test: commands[0] | pylint tuf
************* Module tuf.log
tuf/log.py:176:6: W0128: Redeclared variable 'junk' in assignment (redeclared-assigned-name)
************* Module tuf.client.updater
tuf/client/updater.py:1731:4: W0127: Assigning the same variable 'metadata_filename' to itself (self-assigning-variable)

This PR fixes the issues. See commit messages for details.

Please verify and check that the pull request fulfills the following
requirements
:

  • The code follows the Code Style Guidelines
  • Tests have been added for the bug fix or new feature
  • Docs have been added for the bug fix or new feature

Seems to be an artifact of a feature-removal (compression)
in 8de5c69.

Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
Pylint now has a "redeclared-assigned-name" check that
gets triggered if we re-use our custom "junk" unused var
name. It does not if we use the "_" default unused var name.

So let's use "_" then.

Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
@lukpueh lukpueh merged commit b33ac56 into theupdateframework:develop Sep 24, 2019
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

Successfully merging this pull request may close these issues.

2 participants