Hi Bruno, On 2/26/24 12:38 PM, Bruno Haible wrote: > 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.
I think that option 2 would be the best idea. It seems like all the different Python tools could never agree on a way to configure things. >From the pycodestyle documentation, per project configuration must be placed in setup.cfg or tox.ini [1]. It seems that setup.cfg is a file from setuptools (Python packaging tool) that has mostly superseded by pyproject.toml [2]. Most tools seem to support this pyproject.toml format, but it seems that the pycodestyle people are not fans [3]. The tox.ini file is used to configure tox which is a test automation tool that allows you to run packages with different virtual environments [4]. Seems useful, but a strange place to store configurations. It is my first time learning all this stuff so sorry if it is hard to follow. It is for me as well... I think that it would be best to just shove all the Python mess in that subdirectory since it is a work-in-progress and is safe to be ignored by gnulib users. As long as some gnulib-tool.py file is left in the root directory, it should be easy enough to modify the bootstrap script for testing. [1] https://pycodestyle.pycqa.org/en/latest/intro.html#configuration [2] https://packaging.python.org/en/latest/guides/writing-pyproject-toml/ [3] https://github.com/PyCQA/pycodestyle/issues/813#issuecomment-953736162 [4] https://tox.wiki/en/4.13.0/ Collin
