bind/.pylintrc

[IMPORTS]

deprecated-modules=
    dns.resolver,

[MESSAGES CONTROL]

disable=
    C0103, # invalid-name
    C0114, # missing-module-docstring
    C0115, # missing-class-docstring
    C0116, # missing-function-docstring
    C0209, # consider-using-f-string
    C0301, # line-too-long, handled better by black
    C0302, # too-many-lines
    C0415, # import-outside-toplevel
    R0801, # duplicate-code
    R0901, # too-many-ancestors
    R0902, # too-many-instance-attributes
    R0903, # too-few-public-methods
    R0904, # too-many-public-methods
    R0911, # too-many-return-statements
    R0912, # too-many-branches
    R0913, # too-many-arguments
    R0914, # too-many-locals
    R0915, # too-many-statements
    R0916, # too-many-boolean-expressions
    R0917, # too-many-positional-arguments
Deprecate dns.resolver module in BIND 9 system tests 2024-07-04 20:06:36 +02:00			`[IMPORTS]`

			`deprecated-modules=`
			`dns.resolver,`

			`[MESSAGES CONTROL]`

Add pylint and flake8 tests to GitLab CI Our python code didn't adhere to any coding standard. In this commit, we add flame8 (https://pypi.org/project/flake8/), and pylint (https://www.pylint.org/). There's couple of exceptions: - ans.py scripts are not checked, nor fixed as part of this MR - pylint's missing-*-docstring and duplicate-code checks have been disabled via .pylintrc Both exceptions should be removed in due time. 2020-03-30 14:18:01 +02:00			`disable=`
Disable PyLint warning C0209 PyLint 2.11 reports a new warning, C0209 (consider-using-f-string). Since f-strings are only available in Python 3.6+, existing scripts cannot be updated to use this feature just yet because they would stop working with older Python versions. Instead, disable PyLint warning C0209 for the time being. Sort all disabled warnings in .pylintrc. 2021-10-28 14:03:04 +02:00			`C0103, # invalid-name`
Add pylint and flake8 tests to GitLab CI Our python code didn't adhere to any coding standard. In this commit, we add flame8 (https://pypi.org/project/flake8/), and pylint (https://www.pylint.org/). There's couple of exceptions: - ans.py scripts are not checked, nor fixed as part of this MR - pylint's missing-*-docstring and duplicate-code checks have been disabled via .pylintrc Both exceptions should be removed in due time. 2020-03-30 14:18:01 +02:00			`C0114, # missing-module-docstring`
			`C0115, # missing-class-docstring`
			`C0116, # missing-function-docstring`
Disable PyLint warning C0209 PyLint 2.11 reports a new warning, C0209 (consider-using-f-string). Since f-strings are only available in Python 3.6+, existing scripts cannot be updated to use this feature just yet because they would stop working with older Python versions. Instead, disable PyLint warning C0209 for the time being. Sort all disabled warnings in .pylintrc. 2021-10-28 14:03:04 +02:00			`C0209, # consider-using-f-string`
Silent pylint's line-too-long warning as it's handled better by black Black allows the lines with string literals to be longer, which is convenient for descriptive error messages. 2023-11-02 16:29:46 +01:00			`C0301, # line-too-long, handled better by black`
Disable too-many/too-few pylint checks Enforcing pylint standards and default for our test code seems counter-productive. Since most of the newly added code are tests or is test-related, encountering these checks rarely make us refactor the code in other ways and we just disable these checks individually. Code that is too complex or convoluted will be pointed out in reviews anyways. 2024-10-14 14:44:06 +02:00			`C0302, # too-many-lines`
Disable PyLint warning C0209 PyLint 2.11 reports a new warning, C0209 (consider-using-f-string). Since f-strings are only available in Python 3.6+, existing scripts cannot be updated to use this feature just yet because they would stop working with older Python versions. Instead, disable PyLint warning C0209 for the time being. Sort all disabled warnings in .pylintrc. 2021-10-28 14:03:04 +02:00			`C0415, # import-outside-toplevel`
Add pylint and flake8 tests to GitLab CI Our python code didn't adhere to any coding standard. In this commit, we add flame8 (https://pypi.org/project/flake8/), and pylint (https://www.pylint.org/). There's couple of exceptions: - ans.py scripts are not checked, nor fixed as part of this MR - pylint's missing-*-docstring and duplicate-code checks have been disabled via .pylintrc Both exceptions should be removed in due time. 2020-03-30 14:18:01 +02:00			`R0801, # duplicate-code`
Disable too-many/too-few pylint checks Enforcing pylint standards and default for our test code seems counter-productive. Since most of the newly added code are tests or is test-related, encountering these checks rarely make us refactor the code in other ways and we just disable these checks individually. Code that is too complex or convoluted will be pointed out in reviews anyways. 2024-10-14 14:44:06 +02:00			`R0901, # too-many-ancestors`
			`R0902, # too-many-instance-attributes`
Disable pylint check for too-few-public-methods This check is overly aggressive and not really useful, especially for non-Python codebase, where the primary use of Python is for testing. 2023-04-05 10:48:57 +02:00			`R0903, # too-few-public-methods`
Disable too-many/too-few pylint checks Enforcing pylint standards and default for our test code seems counter-productive. Since most of the newly added code are tests or is test-related, encountering these checks rarely make us refactor the code in other ways and we just disable these checks individually. Code that is too complex or convoluted will be pointed out in reviews anyways. 2024-10-14 14:44:06 +02:00			`R0904, # too-many-public-methods`
			`R0911, # too-many-return-statements`
			`R0912, # too-many-branches`
			`R0913, # too-many-arguments`
			`R0914, # too-many-locals`
			`R0915, # too-many-statements`
			`R0916, # too-many-boolean-expressions`
			`R0917, # too-many-positional-arguments`