yahoo-eng-team team mailing list archive

[Paride Legovini <paride.legovini@xxxxxxxxxxxxx>]

Public bug reported:

The newly released pylint 2.4.0 detects variable self-assignments and
throws a W0127 when one is found. There are four of these self-
assignments in cloud-init, all in this form:

@skipUnlessJsonSchema()
class TestSchema(CiTestCase, SchemaTestCaseMixin):

    with_logs = True
    schema = schema
    ^^^^^^^^^^^^^^^

and all introduced by this commit:

https://git.launchpad.net/cloud-
init/commit/cloudinit/config/tests/test_snap.py?id=5037252ca5

I'd drop them, but it seems they have been introduced on purpose. Is
there a good reason to keep them?

** Affects: cloud-init
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1845489

Title:
  Variable self-assignments causing pylint W0127 (self-assigning-
  variable)

Status in cloud-init:
  New

Bug description:
  The newly released pylint 2.4.0 detects variable self-assignments and
  throws a W0127 when one is found. There are four of these self-
  assignments in cloud-init, all in this form:

  @skipUnlessJsonSchema()
  class TestSchema(CiTestCase, SchemaTestCaseMixin):

      with_logs = True
      schema = schema
      ^^^^^^^^^^^^^^^

  and all introduced by this commit:

  https://git.launchpad.net/cloud-
  init/commit/cloudinit/config/tests/test_snap.py?id=5037252ca5

  I'd drop them, but it seems they have been introduced on purpose. Is
  there a good reason to keep them?

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1845489/+subscriptions