britonad / pylint-errors Goto Github PK

I used the example in bad.py for bad-mcs-method-errors in pylint to improve the documentation and it did not throw an error

This will result in all closures using the same value for the closed-over variable.

def foo(numbers):
    for i in numbers:
        def bar():
            print(i)
        bar()

Using the above code followed by foo([1, 2, 3]) prints

1
2
3

which I believe is expected. It seems all closures are NOT using the same value for the closed-over variable in this example.

• E0014: bad-configuration-section
• C2503: bad-file-encoding
• E0013: bad-plugin-value
• E2502: bidirectional-unicode
• R6003: consider-alternative-union-syntax
• W0160: consider-ternary-expression
• R6002: consider-using-alias
• R6101: consider-using-namedtuple-or-dataclass
• W4901: deprecated-module
• W4902: deprecated-method
• W4903: deprecated-argument
• W4904: deprecated-class
• W4905: deprecated-decorator
• I0022: deprecated-pragma
• W6001: deprecated-typing-alias
• C0104: disallowed-name
• F0001: fatal
• I0013: file-ignored
• W1515: forgotten-debug-statement
• C2701: import-private-name
• W1405: inconsistent-quotes
• E2510: invalid-character-backspace
• E2511: invalid-character-carriage-return
• E2512: invalid-character-sub
• E2513: invalid-character-esc
• E2514: invalid-character-null
• E2515: invalid-character-zero-width-space
• E0306: invalid-repr-returned
• E0307: invalid-str-returned
• E2501: invalid-unicode-codec
• W1116: isinstance-second-argument-not-valid-type
• I0011: locally-disabled
• C2201: misplaced-comparison-constant
• W9021: missing-any-param-doc

Hi,

We have been hard at work integrating the content of this wonderful project into the main pylint project. Progress can be viewed here:
pylint-dev/pylint#5953

I was wondering, would you be willing to add pylint as a sub-module to this project? If we were to do so we would be able to get some of the data from the pylint documentation data instead of getting it from this project. That would remove some of the duplication that will eventually be created between both projects. It will also direct any efforts towards improving examples or documentation to one place instead of across both projects.
The data structure of our new data is explained in the mentioned issue and should be fairly trivial to integrate into the project after pylint has been added as sub-module.

I'd be happy to create a PR to do this!