Collin Funk wrote: > Adding the two attached files to the root directory of gnulib should > adjust the warnings to the agreed upon coding style (as far as > pycodestyle and pylint are concerned). It works with Emacs and Eglot > using pylsp. I assume other editors should work similarly. > > Not sure if they are worth adding to the repository but I figured I > would share them just incase anyone else wants to work on stuff in the > future. > > More information about these files here: > https://pycodestyle.pycqa.org/en/latest/intro.html#configuration > https://pylint.readthedocs.io/en/stable/user_guide/configuration/index.html#
It's a good idea to have these in the git repository, rather than to have each developer install them privately. For pylint, according to https://pylint.pycqa.org/en/stable/user_guide/usage/run.html#command-line-options it's OK to have the file .pylintrc in the gnulib root directory. If this is true (i.e. if it works with the file name '.pylintrc' instead of 'pylintrc' in your environment), feel free to submit this file as a patch. It's OK with me because the file name is descriptive enough and because it's hidden. For pycodestyle, a file named '.pycodestyle' would be OK with me as well, if that works. If not, then how about - submitting a feature request to the pycodestyle developers, so that '.pycodestyle' is accepted in addition to of 'pycodestyle' or 'setup.cfg'? - or, alternatively, can we move the gnulib-tool.py into the pygnulib/ directory, leaving only a small redirector gnulib-tool.py at the top level? Then we could have the 'pycodestyle' or 'setup.cfg' in the pygnulib/ directory. Bruno
