It may be more standard to use a .pylint file to specify pylint overrides. Advantages could be fewer runs of pylint, more standard. Disadvantages could be that all of those exceptions are peppered throughout the code.
Unless it's trivial this doesn't need to be part of this PR, but maybe there's a more generic solution where a .pylint file is placed into each folder with the configuration for that folder? This code could iterate over the folders and run it with the contents of that config file.
It may be more standard to use a .pylint file to specify pylint overrides. Advantages could be fewer runs of pylint, more standard. Disadvantages could be that all of those exceptions are peppered throughout the code.
Unless it's trivial this doesn't need to be part of this PR, but maybe there's a more generic solution where a .pylint file is placed into each folder with the configuration for that folder? This code could iterate over the folders and run it with the contents of that config file.
_Originally posted by @dblock in https://github.com/opensearch-project/opensearch-py/pull/643#discussion_r1446203242_